square_get_order

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

The description only discusses routing details (JWT, tenant, company scope) and the arguments parameter. It fails to disclose behavioral traits such as whether the operation is read-only, what it returns, or any side effects. With no annotations, this is a critical gap.

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 short but includes redundant routing details. It could be more concise and front-loaded with the core function. However, it does not contain excessive fluff.

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?

Despite having an output schema (not shown), the description provides no information about return values. Combined with zero annotations and poor parameter documentation, the description is highly incomplete for a tool that likely retrieves a specific order.

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 single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation', which adds minimal meaning. With 0% schema description coverage, the description does not elaborate on the internal structure or required fields, leaving the agent guessing.

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 labels it as 'Square connector operation get_order' but doesn't explicitly state that it retrieves a specific order. It lacks a clear verb and resource description, and doesn't distinguish from sibling tools like 'square_search_orders'.

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. There is no mention of prerequisites, scenarios, 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.