Orders_getOrderBuyerInfo

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals a deployment constraint but does not explain what that means for invocation, whether the operation is read-only, what data it returns, or whether credentials/permissions are needed. The description is too thin to be transparent.

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 and mostly free of filler, but it is poorly structured: the unhelpful 'Catalog entry' comes first, the confusing deployment note comes second, and the actual purpose appears last. The first two sentences do not earn their place.

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 no input schema details and no output schema, the description needed to be self-sufficient. It fails to explain how to identify the order, what fields of buyer information are returned, or what 'not here' operationally means. The caveat may even imply the tool is not callable in the current environment, further reducing completeness.

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 input schema is empty, yet the description says 'the order that you specify,' implying an order identifier parameter that is not defined anywhere. It gives no parameter name, type, format, or location, so an agent cannot determine how to pass the order. The baseline for zero parameters is not met because the description introduces an unresolved input expectation.

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 phrase 'Returns buyer information for the order that you specify' provides a verb, resource, and object, so the basic purpose is understandable. However, 'Catalog entry' and 'Runs in your Kuudo deployment, not here' are vague and do not clarify what 'buyer information' includes or how this differs from sibling Orders_getOrderItemsBuyerInfo.

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?

The description gives no guidance on when to use this tool versus alternatives such as Orders_getOrder, Orders_getOrderItems, or Orders_getOrderItemsBuyerInfo. The deployment note is environmental context, not a usage criterion, so an agent cannot choose this tool over its siblings confidently.

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