Get Full Kit

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

The description discloses that the tool never raises a protocol error on invalid input, instead returning an error object with fix instructions. It also reiterates the read-only and idempotent nature, reinforcing the annotations with actionable safety 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 well-structured and front-loaded with the main purpose, followed by an example, error behavior, and safety note. Every sentence adds valuable information without 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?

For a simple one-parameter tool, the description covers purpose, usage coordination with list_kits, error handling, access restrictions, and retry safety. It is complete given the rich annotations and full schema coverage.

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 fully documents the slug parameter with an example and origin (list_kits). The description adds a concrete 'typical input' example and previews the output structure, which helps the agent understand the parameter's role beyond the schema baseline.

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 a specific verb ('Load') and resource ('a themed kit and every member product'), clearly distinguishing this from sibling get_full_* tools that focus on individual entities. It also specifies the premium requirement, adding purpose-related context.

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 when to use the tool (to retrieve a full kit and its products) and references list_kits as the source for a valid slug, providing a coordination hint. It does not explicitly exclude alternatives, but the scope is unambiguous.

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