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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral claim is 'privacy-filtered project metadata', which hints at access scoping but is not explained (what is filtered out, or on what authority). Modest added value against a low annotation bar.

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?

It is a single short sentence, so there is no padding, but 'Read hosted get' is noise that muddies the verb rather than front-loading the action. The one substantive clause, 'privacy-filtered project metadata', arrives after the garbled prefix.

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?

Five parameters (four optional filters), no output schema, and no explanation of which optional IDs narrow the result set or how they interact. With the schema descriptions effectively broken by duplication, the description was the only place to compensate and it does not, so an agent cannot confidently build a filtered call.

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 the baseline is 3. The description adds nothing about how projectId, requestId, sessionId, executionId, or presentationId scope the query, and the schema's own descriptions are identical boilerplate ('Owned project ID returned by list_linked_projects...') for all five properties, so neither layer clarifies what each filter does.

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 phrase 'get pending presentation requests' does state a resource and read intent, but it is buried in garbled templated wording ('Read hosted get pending presentation requests'), which reads like a string-substitution artifact. It does not distinguish this tool from close siblings such as get_pending_implementation_meter_changes, get_pending_scope_organizations, or list_presentations.

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 when-to-use condition, no prerequisites, and no named alternative. An agent cannot tell from this description when a pending-request lookup is the right call versus list_presentations or get_presentation. Usage must be inferred entirely from the name.

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