get_fulfillment_services

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Fetch' which implies a read, but does not mention pagination behavior (though the schema has pagination params), return format, or any other operational details. It adds no behavioral context beyond the basic action.

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 a single, concise sentence that is front-loaded with the core purpose. No wasted words.

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 is simple with only two optional params and no output schema, so the description does not need to explain return values. However, the presence of a near-identically named sibling tool (get_custom_fulfillment_services) creates ambiguity that the description does not resolve, making it incomplete for disambiguation.

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 already describes both parameters ('Cursor for pagination' and 'Number of fulfillment services to fetch (1-250, default: 50)'), and the description adds no additional parameter semantics. Since schema coverage is 100%, baseline of 3 is appropriate.

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 'Fetch custom fulfillment services configured in the store' clearly identifies the verb (fetch) and resource (custom fulfillment services), and adds context of store configuration. However, a sibling tool named 'get_custom_fulfillment_services' exists, and the description does not distinguish how this tool differs from that one, so it is not fully distinguishing.

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?

No guidance is given on when to use this tool versus alternatives like get_custom_fulfillment_services or other fulfillment-related tools. There is no mention of exclusions, prerequisites, or the relationship to sibling tools.

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