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

No annotations are provided, and the description 'Pin' reveals nothing about behavior, side effects, authentication, output characteristics, or limitations. The description carries the full burden and fails to disclose anything.

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?

While the description is extremely short, this is under-specification rather than effective conciseness. It lacks any substantive content to structure or front-load, so it does not earn credit for being well-crafted.

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 tool with two parameters and no output schema, the description still needs to convey the core operation. 'Pin' provides no explanation of what the tool does, what it returns, or how to use it, making it completely inadequate for an agent to select and invoke it correctly.

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 fully documents both parameters (url as 'Pinterest pin URL' and trim as 'Set to true for a trimmed down version of the response'), so schema coverage is 100%. The description adds no extra parameter meaning, but the baseline of 3 applies because the schema already provides the necessary semantics.

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 is simply 'Pin', a noun with no verb. It does not state what the tool does, such as scraping or fetching a Pinterest pin, and it merely echoes part of the tool name without explaining the action or resource scope.

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?

There is no guidance on when to use this tool or how it differs from the many sibling scraper tools (e.g., scrapecreators_board, scrapecreators_instagram). No context, prerequisites, or alternatives are provided.

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