EasyShip_createScheduledPackage

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does disclose an important trait: 'Runs in your Kuudo deployment, not here', indicating the tool is not executed in the current context. However, for a scheduling/mutation operation, it does not mention permissions, reversibility, side effects, or failure modes, so behavioral transparency is only partially addressed.

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 front-loaded, placing the 'Catalog entry' and 'Runs in your Kuudo deployment, not here' context before the action. Each sentence adds some information, and there is minimal verbosity. It is efficient, though the 'Catalog entry' phrase could be clearer.

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?

The tool has no annotations, no output schema, and an empty input schema that still allows arbitrary properties. The description does not provide enough information for an agent to know what inputs are required or what the returned scheduled package information looks like. This is only partially adequate for a tool that an agent must select and invoke correctly.

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 declared properties and permits additional properties, so there are no formal parameter definitions to augment. The description names the domain concept ('Easy Ship order') but gives no parameter names, formats, or required inputs. Since the schema is effectively empty, the description should have compensated more for the missing invocation details.

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 action and resource: 'Schedules an Easy Ship order and returns the scheduled package information.' The 'Catalog entry' phrase adds context but is not the core purpose. It is clear enough to distinguish from the general shipping siblings, though it does not explicitly differentiate from EasyShip_createScheduledPackageBulk.

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?

There is no explicit guidance about when to use this tool versus alternatives like EasyShip_createScheduledPackageBulk or EasyShip_updateScheduledPackages. The note 'Runs in your Kuudo deployment, not here' gives an environment constraint but not selection criteria. An agent is left to infer when this specific tool is appropriate.

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