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

With no annotations provided, the description carries the behavioral disclosure burden. It does this well by explicitly stating that the resource always answers and that status: "none" means no erasure was ever requested, so clients never need to interpret a 404 as 'nothing scheduled'. This is valuable behavioral context beyond a generic read description.

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 sentences, front-loaded with the primary operation and followed by the most important behavioral nuance. Every sentence earns its place, with no filler or repetition of schema details.

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 simple one-parameter read operation with no output schema, the description covers the critical edge case that could confuse callers: the difference between 'no deletion ever requested' and a missing resource. It does not enumerate other possible status values or response fields, but the essential invocation and interpretation context is present.

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%, as the only parameter, organization_id, is described as 'Active organization ID'. The description adds no meaningful parameter-level detail beyond that, so the baseline of 3 is appropriate.

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 clearly states the verb 'Read' and the resource 'latest tenant deletion request', making the tool's purpose immediately understandable. It does not explicitly differentiate from sibling tools like commsharbor_deletion_schedule or commsharbor_deletion_cancel, but the read semantics are obvious from the description and name.

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?

The description gives no explicit guidance on when to use this tool versus the related deletion_schedule or deletion_cancel siblings. The intended use is implied by the word 'Read', but there are no stated alternatives, exclusions, or prerequisites beyond the schema-required organization_id.

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