sap_list_all_agents

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

Indicates it reads directly from on-chain program accounts, implying a read-only operation. No annotations exist, so the description must cover this; it does reasonably. However, it omits details like pagination behavior, latency, or data freshness.

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?

Two concise sentences with a clear action and example. No extraneous text. Could be slightly improved with formatting, but effective.

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?

No output schema exists, and the description does not describe the return format or fields. Given 6 parameters and no output guidance, the description is incomplete for an agent to fully understand the tool's behavior.

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 covers all 6 parameters with 100% description coverage. The tool description adds no new meaning beyond the schema, so 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 verb 'Enumerate' and resource 'SAP AgentAccount PDAs' are specific. However, it does not differentiate from the very similar sibling tool 'sap_list_agents', which could cause confusion.

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?

Provides a clear usage example ('list all agents in the SAP ecosystem rn'), but no exclusion criteria or comparison to similar tools like sap_list_agents or sap_get_agent.

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