get_adr_templates

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

The description only states 'No authentication required.' With no annotations, it fails to disclose whether the tool is read-only, caches data, or has any rate limits. The 'Get' verb implies read but is not explicit.

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 sentences, front-loading the purpose and including a key behavioral note (no auth). No unnecessary words.

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?

While the description covers purpose and a constraint, it omits what the output format is (list? text?) and whether the domain filter is exact or partial. Given no output schema, more detail would improve completeness.

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 schema covers 100% of parameters, and the description aligns with the parameter examples (e.g., web_application). However, the description does not add significant meaning beyond the schema's domain list.

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 explicitly states that the tool retrieves domain-specific ADR templates and anti-patterns, listing example domains. This clearly distinguishes it from sibling tools like get_adr_context or get_adr_diagrams.

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 notes that no authentication is required, which is helpful. However, it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or context for usage.

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