Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, non-destructive, open-world behavior, and the description goes further by disclosing the auth requirement (Bearer rh_live_… or x-api-key), the wrapped REST endpoint, and — most valuably — that an empty list still carries dataset_last_written_at, dataset_row_count and warnings so a zero is interpretable rather than ambiguous. It does not discuss pagination behavior beyond what the schema shows.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then endpoint, then access, then a Returns list; the multi-section layout is easy to scan. The Returns bullet list is somewhat verbose for a tool without an output schema, but the empty-list caveat earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description appropriately enumerates the return fields (agent_id, chain, feedback, meta) and explains the diagnostic meta on empty results. Remaining gaps are minor: nothing on result ordering or pagination beyond the clamped limit parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so agentId, chain (CAIP-2, agent id not unique across chains) and limit (clamped to 100) are fully documented in the schema. The description adds no parameter-level detail beyond reiterating that chain identifies where feedback was read, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (raw feedback entries from the ReputationRegistry) scoped to a single agent id, and names the underlying endpoint (GET /v0/agents/{agentId}/feedback). This clearly separates it from get_agent, which returns the agent record rather than its reputation entries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the scope 'for a single agent id,' but there is no explicit when-to-use/when-not guidance and no routing to alternatives (e.g., get_agent for profile data, or a leaderboard tool for aggregate rankings). An agent must infer the correct tool from the name and purpose line alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.