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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the phrase 'privacy-filtered', which hints at result scoping but does not explain what filtering is applied, whether results are paginated, or how much of the inbox is returned.

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 short sentence with no filler and the action front-loaded. It is efficient, though the brevity comes at the cost of substance rather than being paired with useful detail.

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 four-parameter, no-output-schema read tool, the description omits return shape, ordering, filtering semantics, and the relationship between the four ID parameters. The privacy-filtering claim is asserted but never explained, so an agent cannot predict what it will get back.

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 nominally 100%, so the baseline is 3 and the description adds no parameter meaning. Notably the schema's descriptions are identical boilerplate ('Owned project ID...') repeated for taskId, sessionId, and executionId, and the description does nothing to disambiguate these, leaving a real risk of misuse.

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 verb+resource pair ('Read hosted inbox list') is identifiable, but the qualifier 'using privacy-filtered project metadata' is vague and does not clarify what is actually returned. Nothing distinguishes it from nearby siblings such as inbox_claim, inbox_start, or complete_inbox_task.

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 when-to-use guidance at all. With three inbox-related siblings (inbox_claim, inbox_start, complete_inbox_task) plus list_linked_projects and map_project, an agent has no basis for choosing this tool over them.

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