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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds one useful piece of context beyond that: the response includes extraction schema details. It says nothing about error behavior (e.g., what happens with an invalid inbox_id), but the annotation coverage keeps this at an acceptable 3.

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 the resource and the returned payload front-loaded. Nothing is padded or wasted.

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 single-record read protected by rich read-only annotations, the description is close to sufficient, and the note about included schema details clarifies the return payload in the absence of an output schema. However, it omits what identifies the inbox in the response or how a missing inbox is signaled, leaving a modest gap.

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 one parameter, and the schema documents it at 100% coverage ("Airparser inbox id."). The description adds no format or sourcing detail for inbox_id, so it neither helps nor hurts beyond the schema baseline.

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 a specific verb and resource ("Get a single Airparser inbox") and adds scope detail ("including extraction schema details"). The word "single" implicitly contrasts with the list_inboxes sibling, though it doesn't explicitly address overlap with get_extraction_schema.

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?

No explicit when-to-use or when-not-to-use guidance. The reader must infer that a single-inbox fetch is the alternative to list_inboxes, and there is no direction on when to call this versus get_extraction_schema, which the description's mention of schema details could confuse.

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