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

Adds context the annotations cannot carry: heavy throttling at 5/min, an undocumented page size, and the instruction to follow `next` until an empty page. Annotations only declare this a safe read, so this operational detail is the description's real contribution; the return envelope shape is the main thing left out.

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?

Four compact sentences, front-loaded with what is returned, then constraint, then pagination, then rate limit and endpoint. Nothing is repeated from the schema and nothing is filler.

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 8 optional params and no output schema, the description covers the returned fields, pagination termination, and throttling, which are the things an agent would otherwise get wrong. It could still say what the response envelope looks like alongside `next`.

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 coverage is 100% and every parameter is described there, including next.page/next.skip. The description adds only the end condition for pagination (stop on an empty page), which the schema does not state, so it is a modest supplement over an already self-documenting schema.

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?

Opens with a specific verb plus resource ('List kits') and enumerates what each record carries (component lines, optional available quantity and cost), which separates it from list_products. It never names a sibling explicitly, so an agent must still infer the kit-vs-product boundary.

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?

States a precondition ('Needs a modified-time window') but immediately undercuts it with '(defaults to all time)', leaving the agent unsure whether a window is mandatory. No when-not or alternative tool is offered.

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