Discover SAP Agents

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

The description claims 'Read-only SAP SDK wrapper' and 'Use these reads', implying the tool is read-only. However, annotations set readOnlyHint: false, which directly contradicts the read-only claim. This is a serious inconsistency.

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 with no fluff. First sentence states purpose, second gives alternative, third provides context. It is front-loaded and efficient.

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?

The description covers purpose and usage context, and an output schema exists to explain return values. However, the contradiction with annotations undermines completeness, and it does not explain default behaviors for limit and hydrate parameters.

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%, so baseline is 3. The description adds value by grouping filter parameters into 'protocol, capability, or capability list', explaining they are alternative filters. This goes beyond the schema's individual descriptions.

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 the tool discovers agents by protocol, capability, or capability list. It uses a specific verb-resource pair ('Discover agents') and distinguishes from the sibling tool sap_list_all_agents for unfiltered listing.

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 explicitly tells when not to use this tool (for unfiltered listing, use sap_list_all_agents) and provides context for when to use it (inspect chain state before mutations). It does not cover all sibling alternatives but gives clear guidance for the most relevant one.

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