list_formats

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

The description claims 'Read-only', but annotations set readOnlyHint=false and destructiveHint=true, creating a direct contradiction. The description does not disclose the actual behavioral traits beyond annotations, and instead contradicts them, which is highly misleading.

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 two sentences with no wasted words. The first sentence states the main purpose, and the second provides usage context. It is well-structured 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?

Without an output schema, the description should fully explain the return format and behavior. It covers formats and dependency status, but the behavioral claim contradicts annotations, so the description is incomplete and unreliable for an agent.

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 no parameters with 100% coverage, so the description does not need to add parameter meaning. The description explains what the output contains (formats and installation status), which is sufficient.

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 shows all supported document formats and their dependency installation status, with a specific verb 'Show' and resource 'document formats'. It distinguishes itself from siblings like 'list_documents' by focusing on formats.

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 says 'Use this to check which formats are available and diagnose missing dependencies', providing clear when-to-use guidance. However, it does not mention when not to use or suggest alternatives, so it's not a 5.

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