parse_get_role

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

With no annotations, the description carries the full burden. It discloses the auth requirement (master key) and what the tool returns (name, ACL, user relationships). It does not mention error behavior, but as a read-only get operation, this is sufficient. No contradictions with annotations.

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 concise sentences. The first sentence is front-loaded with the purpose, and the second adds a key prerequisite. No fluff or redundancy.

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 get tool with one parameter and no output schema, the description covers the return fields and auth requirement. It lacks error handling details, but it is otherwise complete for the tool's complexity.

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 for the actual parameter (inputSchema) is 0%, so the description must compensate. It explicitly mentions 'objectId' and indicates it identifies the role. This adds semantic value beyond the schema, though it does not describe the nested structure, which the schema provides.

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 ('Obtiene los detalles') and resource ('rol específico'), and specifies the exact output details (nombre, ACL, relaciones con usuarios). This distinguishes it from sibling tools like parse_list_roles (list all roles) and parse_get_object (generic object getter).

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?

It states a clear prerequisite (requires master key), which is useful for when to use it. However, it does not explicitly mention alternative tools or when not to use it. The context (fetch role details by objectId) is clear, but without exclusions, it does not achieve a 5.

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