it.manage_api_tokens

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

With no annotations, the description carries full burden for behavioral transparency. It only states the operations (generate, list, revoke) and a high-level purpose. It does not disclose consequences like immediate invalidation upon revocation, rate limits, or required admin privileges, leaving a significant information gap.

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 sentences, front-loading the key actions. It is efficient without unnecessary words. However, it could be slightly more structured by separating the actions from the purpose, but it remains clear and concise.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is minimal. It does not explain the return format (e.g., token string on generation, list of tokens on list), error conditions, or behavior of the 'scope' parameter. For a management tool, more detail is warranted.

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%, so the baseline is 3. The description adds no extra meaning beyond the schema; it merely restates 'action' as generate, list, or revoke. It does not clarify the 'scope' parameter's effect or provide usage examples.

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 'Generate, list, or revoke API tokens for user accounts', which is a specific verb+resource combination. It also implies the three distinct actions, effectively distinguishing it from sibling tools like it.manage_users which handles user accounts rather than tokens.

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 implies usage for token management but provides no explicit guidance on when to use this tool versus alternatives (e.g., it.manage_users or it.execute_admin_command). It lacks context about prerequisites, authorization needs, or when not to use.

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