Get Free Skill

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description echoes these while adding valuable context about error handling: invalid inputs return an error object rather than raising protocol errors. This goes beyond annotations by describing the exact failure mode 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 concise, with key information front-loaded: purpose, example, error behavior, and idempotency. Every sentence earns its place, with no redundant fluff or excessive 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?

For a simple one-parameter tool with an output schema present, the description covers essential aspects: what it does, example I/O, error handling, and safety. It is complete enough for an agent to use correctly, though it could explicitly differentiate from get_full_skill for added clarity.

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 clear slug description referencing search_catalog, and the description reinforces it with a concrete example ('inbox-zero-assistant') and typical output. This adds practical meaning beyond the schema by showing usage in context.

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 the tool loads a product's free gateway skill with complete instructions, using a specific verb and resource. It distinguishes from siblings like get_full_skill by highlighting 'free' and 'gateway' nature, and provides a typical input/output example.

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 usage context by showing typical input with a slug from search_catalog and mentioning safety to retry, but it does not explicitly state when to use this tool over alternatives like get_full_skill or exclude scenarios. No exclusions or alternative tool mentions are given, so guidelines are implied rather than explicit.

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