xlsx_validate

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

The description adds behavioral context beyond annotations by mentioning the two engines, cell-level reports, a free-tier cap of 10k/mo, and that it runs locally. It does not contradict annotations and provides valuable insight into the tool's operation.

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?

The description is well-structured and front-loaded with the core purpose. It efficiently uses sections for usage guidelines. While somewhat verbose (e.g., 'No other tool can do this' paragraph), the structure aids readability.

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?

Given the simple input schema (one parameter) and no output schema, the description covers purpose and usage well but omits details on parameter encoding and return format. Annotations provide some safety context, but the lack of output description leaves completeness lacking.

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?

The input schema has one parameter (file_b64) with 0% schema description coverage. The description mentions 'LOCAL .xlsx file' but does not explain that the parameter expects base64-encoded file content. This is a significant gap for an agent to correctly invoke the tool.

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 clearly states that the tool performs a cross-engine consistency check on a local .xlsx file, comparing two independent renderers and reporting cell-level divergences. It distinguishes from siblings by noting that no other tool can do this cross-engine validation.

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 explicitly provides 'USE WHEN' (pre-flight check, audit/regression testing) and 'DO NOT USE WHEN' (casual read, use xlsx_read; upload/attached files) sections, giving clear guidance on when to choose this tool over alternatives.

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