get_delivery_profiles

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 only says 'Fetch', implying a read operation, but does not mention pagination behavior, return format, permissions, or potential rate limits. This is insufficient for a no-annotation tool.

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 three words with no waste or redundancy. It is front-loaded and efficiently states the core action. However, it is so terse that it borders on under-specification, which slightly reduces the score.

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?

With no output schema, the description should explain what the tool returns, but it only mentions 'fetch delivery profiles' without describing the structure, pagination, or contents of the returned data. Given the low complexity, the description is barely adequate for selecting the tool but lacks crucial return-value 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 schema already describes both parameters thoroughly: 'after' as a cursor for pagination and 'first' as a number of profiles to fetch (1-250, default 50). Since schema coverage is 100%, the description does not need to add parameter details; it adds no extra meaning but the schema does the heavy lifting.

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 the verb 'Fetch' and the specific resource 'delivery profiles', which distinguishes it from sibling tools like get_delivery_customizations or get_delivery_option_generators. However, it lacks scope details such as what constitutes a delivery profile or how the returned data is structured.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or contextual scenarios. With many delivery-related sibling tools present, the absence of usage direction leaves the agent guessing.

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