square_get_catalog_item

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

The description includes generic routing info (JWT, tenant, company scope) but adds no tool-specific behavioral traits such as idempotency, error handling, or whether it's a read-only operation. With no annotations, the description should carry the burden but fails to do so.

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 very short but wastes space on generic boilerplate (routing path, scope). The tool-specific part is minimal and uninformative. It is under-specified rather than efficiently 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?

Given the existence of an output schema, return values are not required, but the description fails to explain how to identify which catalog item to retrieve. Compared to sibling Square tools, it lacks critical information for effective use.

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?

The only parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which sheds no light on expected structure (e.g., catalog_item_id, include_deleted). Schema coverage is 0%, so the description does not compensate.

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 merely restates the tool name ('Square connector operation get_catalog_item') without explaining what the tool actually does. It fails to specify that it retrieves a catalog item by ID or any other identifier, making it a tautology.

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 is provided on when to use this tool versus alternatives like square_search_catalog or square_get_item. There is no context about prerequisites, common use cases, or when not to use it.

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