List SAP Agents

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint, covering safety and behavior. The description adds that it's a 'Read-only SAP SDK wrapper against the configured Solana RPC and SAP program,' which reinforces the read-only nature and provides context about the execution environment. No contradictions.

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?

Three sentences: purpose and requirement, sibling differentiation, and broader context. Every sentence adds value. No redundancy. Efficiently front-loaded.

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 (5 optional parameters, rich annotations, output schema exists), the description is complete. It covers purpose, usage guidelines, behavioral context, and correctly defers to sap_list_all_agents for global lists. Output schema handles return values, so no additional description needed.

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 coverage is 100% with individual parameter descriptions. The description adds the requirement 'Requires protocol or capability,' implying at least one filtering parameter must be provided, but does not detail parameter syntax or constraints beyond what is in the schema. Baseline 3 is appropriate.

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 clearly states it is a 'Compatibility alias for filtered SAP agent discovery' and distinguishes it from 'sap_list_all_agents' for global snapshot. The verb 'list agents' and resource 'SAP agents' are specific, and the filtering aspect is highlighted.

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?

Explicitly states when to use this tool vs alternative: 'Use sap_list_all_agents for a global on-chain directory snapshot.' Also specifies requirement: 'Requires protocol or capability.' Provides context for usage sequence: 'Use these reads to inspect current chain state before mutating...'

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