square_list_locations

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

The description discloses routing through '/api/tools/invoke' under JWT, tenant, and company scope, providing authentication context. However, with no annotations, it does not explicitly state the operation is read-only, nor does it mention pagination, rate limits, or error behavior, leaving gaps in transparency.

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 concise at three sentences, front-loading the tool identity and routing info. There is no fluff, but the parameter description is too brief, sacrificing clarity for brevity.

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 the tool's simplicity (1 parameter, output schema exists), the description lacks essential detail about the argument structure and usage context. It does not differentiate from siblings or explain how to properly construct the JSON argument, making it incomplete for effective tool invocation.

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 0%, and the description only says 'arguments: JSON string of arguments for the connector operation'. This is vague and does not explain what keys (e.g., location IDs, filters) the JSON should contain, failing to compensate for the low schema coverage.

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 tool name and description clearly indicate it lists Square locations. The description states 'Square connector operation list_locations' and mentions the platform tool ID. While not overly explicit, the purpose is evident and distinguishable from sibling tools like square_list_customers or square_list_payments.

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 this tool versus other list tools or any prerequisites. There is no mention of context, alternatives, or exclusions, leaving the agent to infer based solely on the tool name.

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