ExternalFulfillmentShipments_getShipment

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

With no annotations, the description carries the full burden, but it only discloses that the tool runs in a Kuudo deployment, not here. It does not explain whether this is a read-only operation, what happens when called outside that deployment, what errors to expect, or what the response contains. The environment hint is useful but insufficient.

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 only three short sentences and contains no filler. However, the most important functional information is placed last, after the opaque 'Catalog entry' and 'not here' caveats, so the structure is somewhat suboptimal.

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 output schema, no annotations, and an empty input schema, this description leaves major gaps: how to pass the ID, what response to expect, and whether the tool is even callable in the current environment. The caveat about running in a Kuudo deployment only raises more questions about how an agent should invoke or redirect the call.

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 has zero properties, so the schema provides no parameter information. The description adds that an ID is required ('with the ID you specify'), but it does not specify the parameter name or format. This partial guidance is helpful but leaves a key gap between the described behavior and the empty 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 phrase 'Get a single shipment with the ID you specify' clearly states the verb and resource, and the singular 'a single shipment' distinguishes it from the sibling ExternalFulfillmentShipments_getShipments. However, the opening 'Catalog entry' and 'Runs in your Kuudo deployment, not here' add ambiguity about whether this tool is actually invocable in the current environment, preventing a perfect score.

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 explicit guidance is given about when to use this tool versus alternatives. The note 'Runs in your Kuudo deployment, not here' is a vague environmental caveat but does not tell the agent when to select this tool over any of the many shipment-related siblings, nor does it name an alternative.

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