Normalize Pinterest URL

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral detail beyond those annotations by specifying that the tool removes tracking parameters and produces canonical form, which clarifies exactly what transformation occurs.

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 a single, front-loaded sentence that clearly states the tool's purpose and effect with zero wasted words. It is concise, scannable, and all information is relevant.

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, single-parameter transformation tool with rich annotations and an output schema, the description is complete. It explains what the tool does, satisfies the behavioral expectations, and does not need to elaborate on return values because the output schema is already provided.

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 schema already documents the single 'url' parameter with 100% coverage, including the requirement that it be a complete Pinterest or pin.it URL. The description adds a hint about 'supported' URLs but does not significantly extend beyond the schema-provided meaning, so a baseline score of 3 is appropriate.

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's function: converting a supported Pinterest URL to canonical form and removing tracking parameters. This specific verb+resource combination distinguishes it from siblings like parse_pinterest_url and is_pinterest_url, which have different purposes.

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 (when you need a canonical Pinterest URL without tracking parameters) but does not explicitly mention when not to use it or name alternative sibling tools. The context is clear but lacks direct exclusions or comparison to parse_pinterest_url or is_pinterest_url.

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