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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so safety profile is covered. The description adds 'privacy-filtered project metadata', which hints at a filtering behavior beyond the annotations, but doesn't explain pagination, ordering, or return shape.

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?

A single efficient sentence with no wasted words. Front-loaded with the verb, though it is sparse given the tool's context.

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?

For a filtered-list tool among many queue-related siblings with no output schema and a schema whose sessionId/executionId descriptions are misleading, the description does too little to help the agent distinguish it or understand the filter dimensions it exposes.

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 coverage is 100%, so parameters are documented. However, the schema has a defect: sessionId and executionId carry the projectId description, so all three are described identically 'Owned project ID returned by list_linked_projects'. The description does not clarify the distinct role of sessionId or executionId, failing to compensate for this confusing 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?

States a verb (Read) and resource (hosted list queue items) with a modifier (privacy-filtered project metadata), but 'list queue items' is vague about what queue items are and how this differs from cancel_queue_item, update_queue_item, or delete_queue_history_items.

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 on when to use this versus sibling queue tools (update_queue_item, cancel_queue_item, delete_queue_history_items) or when listing is appropriate. The agent must infer usage entirely.

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