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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the operation's safety profile. The description adds value by specifying response content exclusions (no contacts, quotes, supplier info, internal notes), which is useful behavioral context. However, it does not describe the return structure, format, or other behaviors, leaving some transparency gaps.

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 highly concise, consisting of a single sentence. However, it lacks front-loading of the core purpose and reads as a fragment rather than a structured definition. The short length is appropriate, but the clarity and order could be improved; it is not a clear, well-organized tool description.

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?

The description is incomplete for a simple tool: it does not state the primary function (retrieving status) or describe the return value. It only provides a negative list of what is not included. Given the presence of annotations and a single parameter, a fuller description is expected to explain what the tool returns and under what circumstances it should be used.

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 schema defines requestId with a pattern, but schema description coverage is 0%, so no descriptive text accompanies the parameter. The description refers to 'this key' but does not explicitly link it to requestId, nor does it explain what the key represents or how it should be formatted. With zero schema coverage, the description should compensate by clarifying the parameter's meaning, but it does not.

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 focuses on what is excluded ('no contacts, quotes, supplier information or internal notes') rather than stating the primary action. The verb 'get' appears only in the tool name, not in the description, and the phrase 'minimal receipt' is vague and does not explicitly state that this returns the status of a request. It does not distinguish the tool from its siblings beyond implying a minimal response.

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 instead of the siblings (create_charter_request, get_charter_intake_contract, validate_trip_brief). It does not mention any conditions or alternatives. The only hint is 'Only this key's minimal receipt,' which implies a narrow use case but is not actionable for tool selection.

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