square_payments

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

No annotations are provided, so the description must fully disclose behavior. It only states 'list or create' but does not mention idempotency, authentication scope, rate limits, or potential side effects. For a payment tool, these are critical.

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 at three words, which is efficient but lacks structural content. It is front-loaded with the core function, but loses points for being under-specified rather than truly concise.

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 tool with 11 parameters, a required access token, and no output schema, the description is woefully incomplete. It misses essential context about action-specific requirements, error handling, pagination for lists, and the response format, making it nearly unusable without further documentation.

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 description coverage is only 45%, and the description adds no parameter details beyond what is in the schema. It does not explain when parameters like source_id, amount_money, or idempotency_key are needed, nor does it clarify the nested object structure.

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 or creates Square payments, specifying the verb and resource. However, it does not differentiate from sibling Square tools like square_catalog_list or square_customers, which have similar purposes for other Square resources.

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?

No guidance on when to use list versus create, or when to prefer this tool over alternatives. The description lacks context on prerequisites or exclusions, leaving the agent without decision-making support.

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