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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds context beyond those: it specifies the response includes the authoritative lease state, current expiry, and terminal status after deletion or expiry, and it warns that the lease bearer must travel on the transport rather than in arguments. This is valuable behavioral and security-relevant disclosure.

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?

The description is two sentences with no wasted words. It front-loads the core purpose and return contents, then adds the critical transport/auth constraint. Every sentence earns its place.

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 one-parameter read-only tool with an output schema and annotations already declaring safety, the description covers the important behavioral points: what is returned, terminal states, and where to supply the lease bearer. It does not discuss when to prefer this over sibling tools, but that is largely inferable from the name and sibling list.

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?

The input schema has 0% description coverage, so the description must compensate for the single inbox_id parameter. It only says 'for one inbox,' which does little more than echo the parameter name. It does not explain how to obtain a valid inbox_id, what the pattern implies, or how the parameter maps to the returned lease information.

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 uses a specific verb ('Return') and names the resource ('lease status for one inbox'), and explicitly lists the returned elements: random receive-only address, authoritative lease status, current expiry, and terminal status. This clearly differentiates it from sibling tools like ausca_agent_inbox_read, ausca_agent_inbox_delete, and ausca_agent_inbox_messages.

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 guidance on when to use this tool versus the sibling tools, nor any mention of alternatives or exclusions. The only operational instruction concerns lease-bearer placement on the transport, which is an authentication detail rather than usage selection advice.

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