spraay_agent_wallet_session_key

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

The description adds cost information which supplements annotations. Annotations indicate readOnlyHint=false and destructiveHint=false, so it's a non-destructive mutation. The description does not contradict annotations but does not elaborate on other behaviors like idempotency or error conditions. It adds some value beyond structured fields.

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 very concise, two sentences, with the purpose and cost front-loaded. Every sentence serves a purpose without fluff, making it efficient for quick understanding.

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's complexity (4 required params, mutation, cost), the description lacks context on prerequisites, return values (though output schema exists), failure modes, or the purpose of a session key. More information is needed for an agent to use it effectively.

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 descriptions are trivial ('durationHours parameter'), and the description only says 'Provide the listed fields as typed arguments,' adding no extra meaning. With 100% schema coverage, baseline is 3, and the description does not enhance parameter understanding.

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 'Add session key' as a clear verb+resource, indicating the tool's action. However, it does not explicitly differentiate from sibling tools like spraay_agent_wallet_revoke_key, which may also involve keys. The purpose is clear but lacks sibling distinction.

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 mentions a cost of $0.02 USDC per call, which is a usage guideline, but does not specify when to use this tool vs alternatives (e.g., revoke_key). There is no guidance on prerequisites (e.g., wallet existence) or context for the session key addition.

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