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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds the important consequence — the inbox's previous schema is replaced, not merged — which clarifies the blast radius of the destructive write beyond what the annotation flag alone conveys. It still omits validation/error behavior and permissions.

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?

One sentence, front-loaded with the conversion action and ending with the replacement consequence — no filler, no repetition of the title.

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?

There is no output schema and the description never says what is returned (e.g., the saved native schema or an id). For a destructive, idempotent write on a fairly complex nested field structure, it also says nothing about conversion failures or validation errors, leaving meaningful gaps.

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% and both parameters (inbox_id, fields) are documented in the schema itself. The description only reinforces the OpenAI-style versus native format distinction for the fields payload, adding no details 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?

The description uses a specific verb chain ('Convert ... and save') and names the exact resource ('Airparser extraction schema format', saved to an inbox). It implicitly distinguishes itself from update_extraction_schema by stating the conversion from OpenAI-style descriptions, but never names or contrasts the sibling explicitly.

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 conversion step implies when to use it (you have an OpenAI-style schema rather than a native one), but there is no explicit statement of when to prefer this over update_extraction_schema or get_extraction_schema_format_guide. Usage must be inferred from the tool name and schema shape.

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