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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Revoke' implies an invalidating or destructive action, but the description does not state whether revocation is permanent, whether active integrations will be affected, or whether any special permissions are required. For a destructive operation, this is a meaningful transparency 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 a single five-word sentence with zero filler or redundancy. It is front-loaded and every word carries meaning. There is no unnecessary structure or repetition of schema properties.

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 two-parameter tool with complete schema coverage, the description is minimally viable: the agent knows the action and the input schema supplies the required arguments. However, because this is a revoke/destructive operation with no annotations and no output schema, the description should ideally state consequences like irreversibility or impact on existing API usage. The missing behavioral context keeps it from being fully complete.

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 100%, and both parameters already have clear descriptions: 'API key ID' and 'Active organization ID'. The tool description adds no additional parameter meaning, but the schema already handles this dimension adequately. Baseline 3 is appropriate because the schema, not the description, does the work.

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 'Revoke an API key' uses a specific verb and resource, making the basic purpose immediately clear. It also distinguishes this tool from sibling tools like api_key_create and api_keys, since revoke is a distinct action. However, it adds little beyond what the tool name already communicates and does not mention the organization scoping involved.

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 gives no guidance on when to use this tool instead of alternatives such as commsharbor_api_key_create or commsharbor_api_keys. It does not state conditions, prerequisites, or exclusions. An agent must infer usage entirely from the name and input schema.

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