my_delivery_slots

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

With no annotations supplied, the description carries the full burden, and it does disclose one genuinely useful behavioral fact: authentication is required. Beyond that it says nothing about whether the call is read-only, what happens when the user is unauthenticated, or whether slots are location-dependent. One real disclosure in an otherwise bare profile lands at the minimum-viable level.

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?

Two short sentences with no filler, and the resource statement is front-loaded ahead of the login requirement. It is efficient, though the brevity is partly a symptom of under-specification rather than disciplined trimming.

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?

An output schema exists, so return values need not be explained, and with zero parameters the schema side is trivially covered. The remaining gap is contextual: in a catalog with checkout_timeslots, delivery_info, and fulfilment_selection, the description never positions this tool relative to them, which is the chief thing an agent needs here.

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 tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a parameterless tool applies. No schema ambiguity exists to compensate for.

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 the resource (delivery slots) scoped to the user, so the general intent is comprehensible. However, it uses no specific verb (list/retrieve) and gives no hint of how it differs from near-duplicate siblings such as checkout_timeslots, delivery_info, or my_fulfilment_selection, leaving the agent to guess.

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 when-to-use or when-not-to-use guidance and no alternative tool is named, even though the sibling list contains at least three closely related slot/delivery tools. The only guidance offered is a login prerequisite, which is a condition for calling, not a selection rule.

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