revoke_session_key

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds scope by saying it revokes any active grants for this agent session, but it does not explain reversibility, authorization requirements, or the impact on the current session. The 'preparation_only' tag is also ambiguous in a tool whose action is 'revoke'.

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 core sentence is concise and has no wasted words. However, the action is not front-loaded: the bracketed capability/tier/API metadata comes first and is less useful for invocation decisions than the revoke scope.

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 destructive mutation with four parameters and no output schema, the description is incomplete. It lacks parameter semantics, usage conditions, authorization prerequisites, and a clear statement of what revocation does or does not destroy.

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 0%, and the description mentions none of the four parameters. It gives no meaning for sessionId, agentAddress, sessionToken, or ownerAddress, leaving the agent with only type/pattern constraints.

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 states a specific verb and resource: revoke active session key grants for this agent session. It is distinguishable from siblings such as grant_session_key, session_key_status, and revoke_execution_authority.

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 does not say when to use this tool versus grant_session_key, session_key_status, or revoke_execution_authority. The action is implied, but there is no explicit condition, prerequisite, or exclusion.

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