get_fulfillment_constraint_rules

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

With no annotations provided, the description carries full responsibility for disclosing behavior. The verb 'Fetch' indicates a read-only operation, but the description does not mention pagination behavior, ordering, or what happens if no rules exist. It is adequate but lacks richer behavioral context.

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, short sentence that front-loads the action ('Fetch') and clearly states the resource. Every word contributes to clarity, with no redundancy or unnecessary detail.

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?

This is a simple fetch tool with only two optional pagination parameters, both fully described in the schema. The description alone sufficiently communicates the tool's purpose and scope, making it complete for an agent to select and invoke correctly despite lacking an output schema.

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?

Schema description coverage is 100%, with both 'after' and 'first' clearly documented in the input schema. The description adds no additional meaning beyond the schema, so the baseline score 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 uses the specific verb 'Fetch' and clearly identifies the resource as 'fulfillment constraint rules' with scope 'for the store'. It distinguishes itself from sibling tools like create/update/delete_fulfillment_constraint_rule and other fulfillment tools.

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 implies its usage as a read operation for listing fulfillment constraint rules, but it does not explicitly state when to use it versus alternatives or mention any exclusions. Since there are no obvious alternatives for fetching rules, the context is clear but not elaborated.

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