Get SAP Global State

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

Annotations already declare readOnlyHint=true, idempotentHint=true, etc. The description adds minimal discovery: 'Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.' It confirms the read-only nature but adds limited behavior beyond the annotations. No contradiction.

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 front-loaded with the core purpose in the first sentence. It uses three sentences, the third being slightly verbose but still efficient. Every sentence adds value, though some repetition exists.

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 an existing output schema, the description is fairly complete. It states the action, usage timing, and context. It does not list what the global state contains, but the output schema likely covers that. Minor gap in prerequisites but acceptable.

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?

There are zero parameters, and the description implies a simple, parameterless call with 'Free compact global SAP registry state read.' Schema description coverage is 100% (empty schema), so baseline is 4. No further parameter details needed.

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 uses specific language: 'free compact global SAP registry state read'. It clearly indicates the verb (read) and resource (global SAP registry state). However, it does not explicitly distinguish from sibling read tools like sap_network_stats or sap_fetch_protocol_index, leaving ambiguity about when to choose this 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?

It provides clear context: 'Use for initial orientation before paid network analytics' and 'inspect current chain state before mutating...'. This gives a strong usage hint. However, it lacks explicit exclusions or alternatives, which would raise the score to 5.

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