list_presets

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

Annotations declare readOnlyHint and idempotentHint, so the description does not need to reaffirm safety. It adds no behavioral detail beyond what is in the annotations (e.g., pagination or sorting), but the tool is simple and non-destructive, so this is acceptable.

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 concise sentences, front-loaded with the purpose. Every sentence adds value: the first defines the operation, the second explains the return and usage.

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 no parameters)Skip the description fully explains what is returned and how to consume the results. The presence of an output schema covers return details, and the description means the tool is complete for its simple purpose.

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 takes no parameters, and the schema has none. The description effectively covers the only relevant aspect—what the list contains and how to use the entries. The baseline for 0 params is 4, and the description meets that.

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 'List all available preset screening strategies' and specifies what each entry contains (key, name, description). It differentiates from siblings by mentioning the presets and how to use them with get_preset.

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?

It instructs to use the returned key with get_preset, providing a clear follow-up action. It does not explicitly exclude other contexts, but the guidance is sufficient for a simple enumeration tool.

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