haops_list_role_templates

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

No annotations are present, so the description bears full responsibility. It implies a read-only operation by its nature ('List'), but does not explicitly state that it is non-destructive or safe. It also does not mention any authorization requirements, rate limits, or side effects.

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 concise with two sentences. The first sentence states the purpose directly, and the second adds relevant context. Every word earns its place; no fluff.

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?

The description explains the tool's purpose and what role templates are, but lacks details on output format, pagination, sorting, or whether the list includes both system and custom templates (though implied). For a simple list tool, it is adequate but not fully comprehensive.

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?

Schema description coverage is 100%, so baseline is 3. The description adds no additional parameter guidance beyond what is already in the schema (e.g., 'Free-text search across name + description' and 'Filter by base role bucket'). It does not elaborate on how to use them effectively.

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 the verb 'List' and the resource 'agent role templates', and explains what a role template is and its purpose. It distinguishes from sibling tools like haops_create_role_template or haops_read_role_template by its focus on listing.

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 mentions 'System templates are seeded; admins may publish project-specific custom templates,' providing context on what will be listed. However, it does not explicitly advise when to use this tool versus alternatives like haops_read_role_template or haops_search_help, nor does it specify 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.