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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's only added signal is 'current' (i.e., reflects the latest saved configuration), which is useful but thin; it says nothing about what is returned when no schema is configured or about any permissions needed.

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 front-loaded sentence with zero filler; the verb and resource appear immediately. Nothing needs trimming and nothing is padded.

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-parameter read tool with rich annotations, the definition is close to sufficient. But with no output schema present, the description never says what shape the returned schema takes or how it handles an inbox with no configured schema, leaving the agent to discover that on the first call.

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 (inbox_id) and schema description coverage is 100%, so the schema already carries the full parameter burden and the rubric baseline is 3. The description adds no format, sourcing, or validation detail (e.g., where to obtain an inbox id) beyond what the schema provides.

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 the current extraction schema') scoped to an Airparser inbox, which clearly separates it from the write-side siblings like update_extraction_schema or generate_schema_from_document. It does not, however, explicitly name any sibling or clarify how it differs from get_extraction_schema_format_guide.

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 when-to-use statement, no prerequisites, and no mention of alternatives — notably the closely named sibling get_extraction_schema_format_guide, which an agent could easily confuse this with. The word 'current' hints at reading the live configuration but that is inference, not guidance.

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