haops_transition_role_template

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

No annotations provided, so description must carry burden. Discloses endpoint, error responses (409, 403), condition for system templates, and param naming quirk. Could mention idempotency or side effects, but sufficient.

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?

Front-loaded with purpose, then details. Warning about param naming is important but slightly redundant with schema description. Overall efficient.

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?

No output schema, but description covers lifecycle, constraints, errors, permissions, and verbose flag. For a 3-param tool, it is very complete.

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 covers all parameters (100%). Description adds value by warning that param is named 'action' not 'status', and explains allowed values and verbose parameter effect.

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?

Explicitly states the verb 'transition' and resource 'role template' with specific lifecycle actions (propose/publish/deprecate). Distinguishes from sibling tools like haops_transition_skill and haops_transition_skill_pack by naming the resource.

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?

Describes prerequisites: admin-only, requires ENABLE_COMPOSED_PROTOCOLS=true. Mentions server-enforced state machine and error codes. Does not explicitly compare to alternative tools like haops_update_role_template.

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