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

Annotations already mark readOnlyHint=true and destructiveHint=false; the description reinforces this with 'read-only and safe for hosted mode' and adds the PDA derivation mechanism. However, the boilerplate SAP MCP execution guidance about 'paid builder' and 'finalize unsigned transactions' is not directly applicable to a read-only tool and could confuse agents, slightly reducing clarity beyond what annotations provide.

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 first two sentences are concise and front-loaded. However, the second paragraph is a long, generic SAP MCP execution guidance block that is also duplicated in the input schema, adding redundancy and length without tool-specific value, so not every sentence earns its place.

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?

For a simple read-only batch tool with a well-defined schema and output schema, the description covers the core function, batch limit, and safety. It lacks explicit handling of over-limit inputs or a direct mention of singular alternatives, but these are partially covered by the schema and the sibling list.

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?

The input schema fully describes the 'domains' parameter (array, 1-25, with or without suffix), and schema description coverage is 100%. The tool description repeats the limit but adds no new parameter-specific details beyond behavioral mechanisms.

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 starts with 'Check availability for multiple .sol domains (up to 25) by deriving each SNS PDA and checking account existence on-chain,' which clearly specifies the action, resource, batch scope, and mechanism. It distinguishes itself from the singular sap_sns_check_domain sibling by emphasizing 'multiple' and 'batch'.

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 implies use for multi-domain availability checks and specifies a 25-domain limit, giving some context. However, it does not explicitly mention when to use this batch tool instead of the singular sap_sns_check_domain, and the SAP MCP guidance paragraph is generic infrastructure advice rather than alternative-selection guidance.

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