deadends

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

The description only states the basic function but provides no behavioral details such as whether it is read-only, output format, or performance implications. Since no annotations are provided, the description carries the full burden but fails to disclose important traits.

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, concise sentence that directly conveys the purpose with no extraneous words. It is appropriately front-loaded and efficient.

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 tool has three optional parameters with little schema documentation and no output schema, the description is insufficient. It does not clarify the behavior of 'total' and 'all', nor does it hint at the output structure, leaving an agent potentially confused.

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 description does not mention any of the three parameters (vault, total, all). Schema coverage is only 33% (only vault has a description), and the description does not compensate by explaining what the boolean parameters do, leaving ambiguity.

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: list files with no outgoing links. It uses a specific verb 'list' and resource 'files' with a distinct condition, distinguishing it from siblings like 'links' or 'orphans'.

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?

No guidance on when to use this tool versus alternatives such as 'orphans' or 'unresolved'. The description lacks any context about when it is appropriate or when not to use it.

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