pending_distillates

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds specific filtering behavior (vote_sum >= min_vote, not yet exported) beyond annotations, providing valuable context. No contradiction.

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 concise sentence with no wasted words. It efficiently conveys the tool's purpose and key conditions.

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?

The tool has an output schema documenting return values, so the description need not repeat that. However, the description does not mention ordering or the meaning of 'k', which could be inferred but is not explicit. Overall, it is fairly complete for a simple list 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?

Schema description coverage is 0%, so the description must explain parameters. However, only 'min_vote' is partially explained in the description; 'k' (implying result limit) is not mentioned. This is a significant gap, reducing the ability to use the tool correctly.

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 lists distillates with a specific condition (vote_sum >= min_vote) and that they are not yet exported. The verb 'list' and resource 'distillates' are precise, and the condition distinguishes it from siblings like export_distillates.

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 when to use this tool (to view pending distillates) but does not explicitly state when not to use it or provide alternatives. Given siblings like vote_distill and export_distillates, the usage context is implied but not formalized.

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