Get Full Product

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

Beyond annotations (readOnly, idempotent), the description adds that it never raises a protocol error and returns a structured error object with fix instructions. It also gives an example of the return shape, which is useful 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 moderately sized but every sentence adds value: purpose, premium requirement, example, error behavior, and retry safety. It is well-structured and not unnecessarily verbose.

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 only one parameter and an output schema, the description is very complete. It covers expected output, error handling, premium requirement, and idempotency, leaving little ambiguity for an agent.

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%, so baseline is 3. The description adds value by showing a typical input example and the parameter description clarifies that the slug must be 'exactly as returned by search_catalog,' which helps correct usage.

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 'Load one product in full: persona plus every skill's instructions,' using a specific verb and resource scope. It distinguishes from siblings like get_full_persona and get_full_skill by emphasizing the complete product bundle.

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?

Mentions that this is PREMIUM (paid plan), which is a clear prerequisite/usage condition. Provides typical input and error-return behavior, and explicitly says retry is safe after correcting input. However, it does not explicitly name alternative tools for when not to use this one.

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