Close SAP Agent

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

Annotations already indicate destructiveHint=true. The description adds behavioral context by mentioning prerequisites (signer policy, configured RPC, active SAP profile) and the effect of reclaiming rent. This is valuable beyond the annotations.

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 three sentences. The first sentence clearly states the core action, but the subsequent sentences about MCP context and read/write tools are somewhat generic and not essential for this tool. Still, no fluff.

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 no parameters and the presence of an output schema (not shown but exists), the description covers the action, effect, and prerequisites. It could elaborate on what reclaiming rent means, but overall it is sufficient for an experienced agent.

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?

The tool has no parameters, so schema coverage is 100%. With zero params, baseline is 4. The description does not need to add parameter info, and it correctly avoids doing so.

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 the action clearly: 'Close the connected wallet SAP agent and reclaim rent.' It uses a specific verb and resource, and the mention of 'reclaim rent' distinguishes it from similar tools like deactivate agent. The title reinforces this.

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 when wanting to close the connected wallet's SAP agent, but does not explicitly state when to use it versus alternatives like sap_deactivate_agent. No exclusion criteria or alternative tools are mentioned.

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