spreedly_gateway_list_supported

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

Annotations already mark readOnlyHint=true, and the description reinforces this with 'ONLY reads reference data'. It adds that the tool returns capabilities, which is useful beyond annotations. No mention of rate limits or other side effects, but appropriate for a simple read operation.

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 extremely concise with two sentences, no wasted words. The first sentence states the primary action, and the second provides a reassurance about read-only nature. 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?

Given no parameters and no output schema, the description sufficiently explains what the tool does and what it returns. It covers the purpose and behavior completely for a simple list tool. No additional details are 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?

No parameters exist, so schema coverage is 100% by default. The description adds value by hinting at the output (available integrations and capabilities), which compensates for the lack of an output schema. Baseline for 0 parameters is 4.

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 lists all supported gateway types and their capabilities, using a specific verb 'lists' and resource 'gateway types supported by Spreedly'. It distinguishes from siblings like spreedly_gateway_list which lists user-specific gateways.

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 this is a read-only reference tool but does not explicitly state when to use it versus alternatives like spreedly_gateway_list. The 'ONLY reads reference data' provides some guidance but lacks direct comparison.

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