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

Annotations already mark readOnlyHint=true, so the tool is read-only. The description adds that it returns name, description, and step count, but does not disclose pagination behavior, ordering, or any limits. Since there are no parameters, the behavior is straightforward, but more detail (e.g., 'returns all saved chain recipes') would improve transparency.

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 a single clear sentence that front-loads the purpose and details. Every word is necessary; there is no redundancy or extra information.

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?

For a simple list tool with no parameters, the description adequately specifies what is returned. However, the lack of an output schema means the agent must infer the exact format. The description could be considered complete given the tool's simplicity, but it is missing potential context like whether the list is paginated or sorted.

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?

There are no parameters, and schema description coverage is 100%, so the baseline is high. The description does not need to add parameter information, and it correctly omits any. A score of 4 reflects that no improvement 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 clearly states the verb 'List', the resource 'saved chain recipes', and the fields returned ('name, description, step count'). It is specific and distinguishes the tool from others (e.g., factory_stations lists factory stations, not chain recipes).

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 implies the tool should be used to view saved chain recipes, but it does not provide explicit guidance on when to use it versus alternatives (e.g., other list tools) or when not to use it. No exclusions or prerequisites are mentioned.

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