get_role_guide

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

No annotations are provided, so the description carries the full burden. It discloses it reads from a template and returns a guide, implying read-only behavior. However, it incorrectly marks caller_agent_id as required in text while schema says optional, and does not explain error conditions. No side effects are mentioned.

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 short, well-structured with sections for Args and Returns, and uses bullet points. It is efficient with 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?

For a simple retrieval tool, the description covers the purpose, parameters, and return type. The presence of an output schema reduces the need to detail the return structure. Minor gaps like error handling are acceptable given the tool's simplicity.

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 0%, so the description must add meaning. It adds valid values for role ('owner, admin, worker'), which is helpful. For caller_agent_id, it says 'required' contradicting the schema (optional with default null). This adds some value but with inaccuracy.

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 tool retrieves a role-specific behavior guide from a template file. It specifies the resource (role guide) and action (get), distinguishing it from siblings like list_role_guides which lists guides.

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 basic usage context by listing arguments and return type, but does not explicitly state when to use this tool versus alternatives (e.g., list_role_guides for listing). No exclusions or prerequisites are mentioned.

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