FulfillmentInbound_getSelfShipAppointmentSlots

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does imply a read-only operation with 'Retrieves,' but the statements 'Catalog entry' and 'Runs in your Kuudo deployment, not here' are vague and leave the agent uncertain whether the tool is even callable in the current environment. It also does not disclose return format, authentication needs, or side effects.

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 very short, which is good, but the first two fragments, 'Catalog entry' and 'Runs in your Kuudo deployment, not here,' are unhelpful and potentially confusing. The core action is clear but arrives after ambiguous caveats, so not all sentences 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 zero-parameter, read-only tool with no annotations and no output schema, the description should clarify the slot lifecycle and its relationship to generateSelfShipAppointmentSlots and scheduleSelfShipAppointment. The 'not here' caveat raises more questions than it answers, and no mention is made of prerequisites or what the returned list represents beyond a vague warehouse drop-off context.

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 parameters and schema description coverage is 100%, so parameter documentation is not needed. The baseline for a zero-parameter tool is 4, and the description adds a small amount of useful context by specifying that the slots are for dropping off a shipment at a warehouse.

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: 'Retrieves a list of available self-ship appointment slots used to drop off a shipment at a warehouse.' This distinguishes it from scheduling or cancelling an appointment. However, it does not explicitly differentiate it from the sibling generateSelfShipAppointmentSlots, and the opening 'Catalog entry' phrasing adds ambiguity.

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 call this tool versus alternatives. In particular, sibling FulfillmentInbound_generateSelfShipAppointmentSlots exists, but there is no mention that slots must first be generated or that this get operation is the follow-up read. No exclusions or prerequisites are stated.

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