list_schemas

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool reads under S1000D_SPEC_DIR, inspects brex.xsd for the issue, and reports available schema names, but it does not explicitly state that the operation is read-only, how failures are reported, or what the output structure looks like.

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, front-loaded with the purpose and followed by the diagnostic use case. The parenthetical detail about xml_schema_flat/ and brex.xsd is dense but earns its place by specifying exactly what is inspected.

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 diagnostic listing tool with no output schema, the description is largely complete: it explains what is listed (schema folders), what is read from brex.xsd (the issue), what names are available, and when to use it. A minor gap remains around output format or empty-result behavior.

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 does not need to explain parameters because none exist.

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 uses a specific verb+resource ('Show which S1000D XML schema folders ... were found under S1000D_SPEC_DIR') and adds concrete diagnostic details about brex.xsd and schema names. It does not explicitly distinguish itself from sibling tools like validate_schema or verify_csdb, so it falls short of a 5.

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 clear usage context: 'Use it to diagnose schema-not-found results.' That tells the agent when this tool is appropriate, but it does not name alternatives or say when not to use it.

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