list_deleted_projects

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

Annotations declare read-only, non-destructive. Description adds behavioral nuance: lists only deleted projects, requires `since`, and reveals that some records may be partially restricted (`restrictedKases`). No contradiction. Good additional context beyond annotations.

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?

Two focused sentences, front-loads purpose, no wasted words. Earns its brevity.

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?

Lacks output schema. Description mentions `restrictedKases` but does not describe the main response structure (list of project objects), pagination behavior, or sorting. Leaves significant ambiguity for agent.

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?

Only 33% schema coverage. Description reinforces `since` requirement and adds format example, but provides no semantics for `page` or `perPage` parameters. Fails to compensate for missing schema descriptions on the other two parameters.

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 specific verb+resource: 'list projects deleted on or after a given timestamp'. Differentiates from sibling 'list_projects' (active projects) and 'list_deleted_opportunities' (different entity).

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?

Provides context ('Audit feature') implying use for reviewing deletions, and emphasizes required `since` parameter. However, does not explicitly state when to use alternatives like `list_projects` or `get_projects`, nor provide when-not-to-use guidance.

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