list_global_gateways

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

Describes the HTTP method (GET), return fields (gblGatewayId, name, keyName, requiredFields, fieldDetails), and implies no side effects. Lacks details on pagination or limits, but the simplicity of the tool (no params) makes it adequate.

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 sentences, first stating purpose and examples, second explaining usage and return structure. No wasted words, well-organized.

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, but description lists all returned fields. Tool is simple with no params or nested objects; the description fully covers what an agent needs to know.

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 in schema, so baseline is 4. Description adds no parameter info, which is acceptable since none exist.

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?

Clearly states 'List available global gateway types' with examples (Stripe, Braintree) and specifies the HTTP method and return fields, differentiating its role as a prerequisite for create_gateway.

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 says 'Use this before create_gateway' to discover valid gblGatewayId and required keys, providing clear usage context. Does not mention alternatives or when not to use, but the guidance is strong.

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