set_agent_role

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

No annotations provided, so the description carries the behavioral transparency burden. It discloses authentication requirements (admin key) and a constraint (sandbox agents exclusion). However, it does not describe the effect on the agent's existing permissions, whether the role change is immediate, or any return value. Adds some useful context but leaves gaps.

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?

Two sentences with no extraneous words. Information is front-loaded and efficiently packed.

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 tool with 2 parameters and no output schema, the description covers the essential: purpose, role options, required key, and an edge case (sandbox). Could be more explicit about the result (e.g., success confirmation) but is sufficient for correct invocation.

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 coverage is 100%, baseline 3. The description adds value by explaining the meaning and scope of each role enum value, which goes beyond the schema's 'Role preset to apply' description. The agent_id parameter is not elaborated beyond the schema.

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 'set an agent's role' and lists the three distinct role options with brief scope explanations. This uniquely identifies the tool among siblings, as no other tool deals with role assignment.

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?

Explicitly requires admin key and states that sandbox agents cannot be assigned a role. Provides clear context for when to use (role assignment) and an important exclusion (sandbox agents). Missing explicit alternatives, but the context is sufficient.

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