EasyShip_listHandoverSlots

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

With no annotations, the description must carry the behavioral burden. It discloses that the operation returns data and mentions a deployment caveat ('Runs in your Kuudo deployment, not here'), but it does not clarify side effects, required authentication, or the meaning of the 'Catalog entry' label. This is adequate but not rich.

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 functional sentence is concise and informative, but the opening 'Catalog entry. Runs in your Kuudo deployment, not here' is cryptic and not clearly self-explanatory. A more front-loaded and explicit statement of the invocation context would improve the structure.

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 annotations and no output schema, the description leaves several gaps: the exact invocation environment is unclear, no return structure is described, and the input specification is only high-level ('weight and dimensions'). The tool is low-complexity, but the cryptic 'not here' phrase makes it incomplete.

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 properties, yet the description indicates that package weight and dimensions influence the returned slots, which is the only parameter information available. This meaningfully compensates for an empty schema, though it stops short of specifying parameter names or formats.

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 clearly states a verb and resource: 'Returns time slots available for Easy Ship orders'. It also names the selection criterion (package weight and dimensions), which distinguishes it from nearby sibling tools like EasyShip_createScheduledPackage. However, the opening 'Catalog entry. Runs in your Kuudo deployment, not here' introduces ambiguity about whether the tool is directly invocable, which slightly detracts from clarity.

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 implies the tool is for retrieving handover slots before scheduling an Easy Ship order, based on package dimensions. It does not, however, name any alternative tools or state when not to use it, so the usage guidance remains implicit rather than explicit.

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