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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a meaningful qualifier ('privacy-filtered project metadata') that hints at what the response will contain, but it does not disclose pagination, filtering behavior, or what 'pending' means beyond the name.

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 description is short, but the phrasing 'Read hosted get pending presentation requests' is awkward and unclear rather than cleanly concise. The sentence does not earn its place because it mostly repeats the tool name and adds confusion.

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 five parameters, no output schema, and no usage guidance, the description is far from complete. It gives no sense of what a returned request looks like, how the optional parameters act as filters, or how this differs from related presentation tools.

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 the description adds no meaning to any of the five parameters. It does not explain that projectId is required, nor does it clarify the roles of requestId, sessionId, executionId, or presentationId. With zero schema coverage, the description was the only place to compensate, and it fails to do so.

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 reads as a near-tautology: 'Read hosted get pending presentation requests' essentially restates the tool name without defining what the tool actually does or returns. The phrase 'hosted get' is grammatically garbled, and there is no differentiation from siblings like list_presentations or get_presentation.

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?

No guidance is given on when to use this tool versus alternatives such as create_presentation_request, fail_presentation_request, publish_presentation_request, or list_presentations. There are no exclusions, prerequisites, or context clues beyond the name itself.

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