square_catalog_list

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not mention that access_token is required (though schema notes it), nor does it explain pagination via cursor, rate limits, or return behavior. The description only implies read-only listing but lacks depth.

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 a single sentence with no superfluous words. It is efficiently front-loaded with the core purpose and example types.

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 4 parameters and no output schema, the description is insufficient. It does not explain return format, pagination, or required credentials. The main gap is the lack of explanation for 'access_token', 'cursor', and 'limit'. Sibling tools exist but are not referenced.

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 25% (only 'types' has a description). The description adds minimal value: it lists example object types (items, categories, taxes) which map to 'types', but does not explain 'cursor', 'limit', or that 'access_token' is required. The agent gains little beyond the schema.

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 verb 'List' and the resource 'Square catalog objects', with examples of object types like items, categories, taxes. It distinguishes the tool's purpose as a listing operation, which contrasts with the sibling 'square_catalog_search' (likely a search variant).

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 alternatives like 'square_catalog_search'. No mention of prerequisites (e.g., access_token) or context. The description does not help the agent decide if this is the right tool for the task.

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