list_schemas

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

With no annotations, the description carries the behavioral disclosure burden. It adds valuable context: 'Cheap, offline, and no network' tells the agent this is a low-cost, safe first call. It does not explicitly say 'read-only', but the listing/lookup wording and zero mutation implications make that reasonably clear.

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 very short, front-loads the core purpose, and uses a second sentence for actionable guidance. No filler or redundant restatement of the tool name.

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 zero-parameter catalog tool, this is nearly complete: it states what is listed, when to call it, and why it is safe/cheap. It does not explicitly describe the output format, but the name and phrasing make the return value self-evident.

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 baseline is 4. The description goes further by explaining how its output informs what to pass to template_fields and vocabulary, which helps the agent understand the tool's role in the broader workflow.

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 states the resource clearly: chain steps and vocabularies the server can look up. It lacks an explicit imperative verb like 'lists' or 'returns', but the meaning is unambiguous and distinct from the lookup-focused sibling tools.

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 explicitly says 'Call it first if you are unsure what to pass to template_fields or vocabulary', naming the exact sibling tools and the condition that triggers this tool. This is strong, actionable usage guidance.

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