Orders_getOrderAddress

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, and it adds little. It conveys only that the tool runs elsewhere and returns an address; it does not state whether restricted data access is required (likely for shipping addresses), error behavior, or that the operation is read-only. The 'Runs in your Kuudo deployment, not here' phrasing is ambiguous and could mislead an agent about whether the tool is actually callable.

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 the core action is one sentence, but roughly half of it is filler: 'Catalog entry.' and 'Runs in your Kuudo deployment, not here.' These phrases do not earn their place and add confusion rather than value. A tighter description would drop the preamble and focus on the resource and input.

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 no annotations and no output schema, the agent needs the description to compensate, but it does not. Critical information is missing: how to specify the order (parameter name/format), whether a restricted data token is required, and what the returned address structure looks like. The deployment note is not actionable for invoking the tool.

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 defines zero parameters (only additionalProperties: true), so the baseline is 4. The phrase 'the order that you specify' adds the useful hint that an order identifier is required, but it does not name or format that parameter, leaving the agent to guess what input to send. Some meaning is added beyond the empty schema, but not enough to reliably construct a call.

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 states a specific verb and resource: 'Returns the shipping address for the order that you specify.' This distinguishes it from nearby siblings like Orders_getOrderItems and Orders_getOrderBuyerInfo. However, the preamble 'Catalog entry. Runs in your Kuudo deployment, not here' is confusing and somewhat muddies the otherwise clear purpose.

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 given on when to use this tool versus alternatives such as Orders_getOrder, Orders_getOrderBuyerInfo, or the many Shipping_* tools. The only contextual note ('Runs in your Kuudo deployment, not here') is about deployment, not selection criteria, and does not help an agent decide between siblings.

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