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

No annotations exist, so the description carries the full burden; it discloses that the tool is a catalogue lookup returning per-technology capability flags and a documentation link, which is exactly the behavioral context needed for a zero-argument, side-effect-free call. It stops short of stating read-only/safety properties or the response shape (list vs map) explicitly, keeping it below a 5.

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?

Two sentences with no filler: the first front-loads what is returned, the second delivers the when-to-use routing. Every clause earns its place and nothing repeats structured fields.

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?

With no parameters, no annotations, and no output schema, the description supplies the missing pieces an agent needs: what the listing contains and how to act on it. Nothing required to call it correctly is absent.

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 zero parameters and the schema is an empty object, so there is nothing to disambiguate. The description correctly adds no parameter prose and instead spends its words on output content, which is the right call for a no-argument tool.

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 pairs the specific verb 'List' with a precise resource ('the configuration technologies YAMLTools understands') and even states what each entry contains (validation, diagram, risks, conversions, documentation link). It explicitly distinguishes this catalogue tool from the action siblings analyze_config, config_diagram, and convert_config.

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 gives an explicit trigger ('Call it to decide whether analyze_config, config_diagram or convert_config can help with a file'), naming the alternatives and the decision it resolves. An agent knows to reach for this before selecting one of the three analysis/conversion tools.

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