xlsx_healer_diagnose

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

Annotations already declare read-only and idempotent. Description adds detail on output structure (five finding classes with ref_id keys) and input requirement (source bytes, no reconstruction from spec). No contradictions.

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?

Efficiently structured: purpose statement, enumerated findings, usage guidance. No redundant text. Front-loaded with main action.

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?

Single parameter description implicitly clear. Covers purpose, output structure (five finding classes with reference_ids), usage scenarios, and exclusions. No missing needed context for agent to decide.

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 lacks any description for file_b64. The description indirectly explains it's the source bytes of the .xlsx file, but doesn't specify encoding or constraints. Adds some value over schema but leaves gaps.

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?

Clear verb+resource with enumerated finding types. Explicitly distinguishes from sibling xlsx_data_clean and indicates relationship to healer_cure. No ambiguity.

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?

Explicit when to use with concrete examples, and when not to use with alternative tool named. No gaps.

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