xlsx_properties

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds valuable context: the tool reads specific XML files (docProps/core.xml, app.xml, custom.xml) and does not modify data, confirming its read-only nature.

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-organized with clear sections and usage guidance. Some redundancy exists (e.g., repeating 'core' vs specific fields), but overall it is concise and front-loaded.

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 parameter and no output schema, the description fully covers purpose, usage, behavioral context, and alternatives. It is self-contained and sufficient for an agent to correctly invoke the tool.

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 single parameter file_b64 has no schema description (0% coverage). The description only mentions 'from a LOCAL .xlsx file' but does not explain that the parameter is a base64-encoded string, which is critical for correct usage.

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 the tool's purpose: to surface the workbook's identity card from a local .xlsx file, listing specific properties and sources. It distinguishes from siblings like xlsx_read and xlsx_redact by specifying when not to use them.

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?

Explicitly states when to use (auditing, stripping metadata, extracting custom flags) and when not to use (just reading values, modifying metadata), with clear sibling alternatives (xlsx_read, xlsx_redact).

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