pinterest_create_pin

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

With no annotations, the description carries the disclosure burden. It usefully explains that Pinterest fetches the image server-side and that local file paths will not work, which is a non-obvious behavioral trait and common failure point. It does not cover permissions or response behavior, but the key operational trap is disclosed.

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?

Two sentences with no wasted words. The action is front-loaded, and the essential constraint about public URLs is placed immediately after.

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 creation tool, the description communicates what is being created and the most important prerequisite for successful invocation. It does not describe the return value, but with no output schema and a fairly self-explanatory create operation, the missing return info is a minor gap.

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 description adds critical meaning for image_url by requiring a publicly reachable URL. However, schema description coverage is only 43%, and the description does not clarify ambiguous parameters like board_section_id or further explain title, description, and link semantics 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 opens with a specific verb and resource: 'Create a pin on one of your boards.' This clearly identifies the action and distinguishes it from sibling read/list tools like pinterest_list_pins or pinterest_get_pin_analytics.

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 establishes clear usage context — you use this when creating a pin on an owned board. It does not explicitly name alternatives or when-not-to-use cases, but the creation intent is unambiguous against the read/search/list siblings.

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