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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral detail: 'on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ...}' and 'Every call is read-only and idempotent, so after correcting the input it is always safe to retry.' This goes beyond annotations by explaining error handling and retry safety.

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: first sentence states purpose, then PREMIUM note, then typical input/output, usage guidance, error handling, and idempotent note. It is front-loaded with the most critical information. While slightly verbose, every sentence adds value without redundancy. Could be trimmed slightly, but it remains clear and organized.

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?

Given the tool has only one parameter and an output schema exists, the description covers the expected return structure ('persona plus every skill' with a typical output example), error handling, and sibling references. It is complete enough for an agent to use effectively. The only minor gap is that the full output schema is not detailed, but the presence of an output schema compensates.

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 reinforces the parameter meaning by showing a typical input example: '{"slug": "inbox-zero-assistant"}' and restates that the slug is exactly as returned by search_catalog. However, it does not add new semantic information beyond what the schema already provides.

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 explicitly states 'Load one product in full: persona plus every skill's instructions.' It also provides a typical input/output example and distinguishes from siblings by noting 'Not for a single skill (get_full_skill) and not for a bundle of products (get_full_kit).' This leaves no ambiguity about what the tool does.

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 gives clear guidance: 'Use when the caller wants the whole product.' It also explicitly tells when not to use it by naming alternatives: 'Not for a single skill (get_full_skill) and not for a bundle of products (get_full_kit).' Additionally, it notes the tool is PREMIUM (paid plan), providing context for accessibility.

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