list_heuristics

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

With no annotations, the description must fully explain behavior. It only states 'All registered heuristics' without disclosing that the tool is read-only, what the return format is, or any side effects. The name implies listing, but behavioral traits are absent.

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 extremely brief (6 words) but lacks essential details beyond the name. While not verbose, it is under-specified for an AI agent that may need to understand the tool's purpose without relying on the name alone.

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 simplicity (no parameters, no output schema), the description is incomplete. It does not specify whether the result is a list of names or full objects, or if there are pagination limits. An agent might need more context to use the output correctly.

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 tool has zero parameters, so the schema coverage is 100% trivially. Per the guidelines, baseline is 4 for zero-parameter tools. The description adds no parameter information, but none is needed.

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 'All registered heuristics' clearly indicates that the tool lists all heuristics. The name 'list_heuristics' explicitly conveys the action and resource. However, it lacks differentiation from siblings like 'get_heuristic' or 'match_heuristics', but the purpose is unambiguous.

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 usage guidance is provided. There is no indication of when to use this tool versus alternatives such as 'get_heuristic' for a specific heuristic or 'match_heuristics' for searching. The description offers no context for decision-making.

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