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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond a pointer to describe_operation — no note on what happens when the ID does not exist, whether expansions or includes are supported, or what the response contains.

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?

The same endpoint sentence is repeated verbatim, then an operation ID is appended — the length is padding rather than information. Nothing is front-loaded as actionable guidance; the only real content is the trailing describe_operation pointer.

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, 0% parameter documentation, and a nested 'query' object, the description leaves the agent without the information needed to construct a correct call or interpret the result. The describe_operation pointer is the sole useful context.

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 0% and there are two parameters (path param 'id' and a free-form 'query' object). The description mentions ':id' only as part of the URL string and says nothing about the 'id' format, length constraints, or the semantics of the 'query' object, so it does not compensate for the undocumented schema.

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?

The description only restates the endpoint path 'GET /api/pbc-requests/:id' twice, which duplicates the tool title 'pbc-requests: GET /api/pbc-requests/:id' rather than explaining the purpose in agent-facing language. An agent can infer it fetches a single PBC request by ID, but there is no statement of what a PBC request is and no differentiation from siblings like get_pbc_requests (list) or get_pbc_requests_summary.

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?

There is no guidance on when to use this tool versus get_pbc_requests (list), get_pbc_requests_summary, or execute_read. The only routing hint is 'describe_operation provides native request schemas', which points to a schema-discovery sibling but says nothing about selection conditions.

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