otp_rules_for_role

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

No annotations are present, so the description must convey behavioral traits. It indicates a read operation ('get') but does not disclose any potential side effects, authorization requirements, or data limits. While the name suggests safe retrieval, more explicit transparency would improve trust.

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, front-loading the purpose and value. Every word contributes meaning without redundancy or verbosity.

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 simple retrieval tool with no output schema, the description conveys enough context for an agent to use it appropriately. Minor gaps include lack of detail about return format or pagination, but overall it is sufficient.

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 50% (only 'role' has a schema description). The tool description does not elaborate on parameter meaning beyond the schema, leaving 'limit' unexplained. Given low coverage, the description fails to compensate fully.

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?

Description clearly states the tool retrieves rules and learnings for a specific role, incorporating a verb and resource. It is distinct from sibling tools like otp_network_learnings by emphasizing role-specificity, but does not explicitly differentiate from all siblings.

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 provides a use case (building an agent, inheriting wisdom) but lacks guidance on when not to use the tool or comparisons to alternatives such as otp_search_best_practices. Usage context is implied rather than fully stated.

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