Get SAP Agent Stats

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds context: 'Read-only SAP SDK wrapper against the configured Solana RPC and SAP program' and 'Use these reads to inspect current chain state before mutating...', which reinforces the read-only nature and provides background on how the tool fits into workflows.

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 short, front-loaded with the core functionality, and contains no wasted words. Every sentence adds value, making it easy for an AI agent to parse quickly.

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 presence of an output schema and comprehensive annotations, the description is complete. It mentions the read-only nature, the workflow position (after other agent tools), and the broader context of inspecting chain state before mutations.

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% (agentPda is described). The description does not add extra semantics beyond what the schema provides; it only restates 'by agent PDA'. Baseline is 3 as schema already covers the parameter.

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 'Free exact SAP agent stats read by agent PDA', clearly indicating the verb (read) and resource (SAP agent stats). It also distinguishes from siblings by stating 'Use after sap_get_agent or sap_get_agent_profile when stats are needed', providing specific context for when to use this tool over others.

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 provides explicit usage guidance: 'Use after sap_get_agent or sap_get_agent_profile when stats are needed'. It does not mention when not to use it, but the context is clear enough for an AI agent to select the tool correctly.

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