Promote a user to admin

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

The description adds the key behavior that omitted rights fields default to false, complementing the idempotent and open-world annotations. It does not contradict the annotations and provides useful context for partial updates.

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, front-loaded with the primary purpose, 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 moderate-complexity tool with nested parameters, the description covers the core action and default behavior but omits prerequisites, return values, and error scenarios. It is sufficient for basic usage but not comprehensive.

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?

With only 20% schema description coverage, the description compensates by clarifying the rights object semantics (omitted fields default to false), but leaves peer, user, and accountId without explanation, relying on their names.

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 'Grant admin rights' with a specific verb and resource, distinguishing it from sibling tools like demote_admin that revoke admin rights.

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 no explicit guidance on when to use this tool versus alternatives like demote_admin, though the purpose is clear. It focuses on how to pass rights fields rather than when to invoke it.

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