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 covered. The description adds real value by concretizing the destruction: 'Fields not included are removed from the schema' tells the agent exactly what data loss results from a partial fields array, which the annotations alone do not convey.

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 action and immediately followed by the destructive consequence. Nothing is wasted and the most important warning comes before any elaboration.

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 destructive replace operation with no output schema, the description covers the critical behavior (full replacement, omitted fields deleted) and annotations cover idempotency and destructiveness. It could have pointed to get_extraction_schema_format_guide for the exact native format, which is the one remaining gap an agent would face.

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 coverage is 100%, so the baseline is 3. The description goes slightly beyond by clarifying that fields is a full-replacement payload in Airparser's native validated format, which explains the semantics of the array rather than just its shape.

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 (replace) and resource (extraction schema of an Airparser inbox) and hints at format differentiation from the sibling update_extraction_schema_from_json_schema via 'native validated schema format'. However, it never names that sibling, so the distinction relies on the reader inferring the format contrast.

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 implies you should use this when you already have fields in Airparser's native format, but it gives no explicit when-to-use vs get_extraction_schema_format_guide or update_extraction_schema_from_json_schema. Usage is inferable rather than stated.

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