Create a Pinterest board

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

Annotations already indicate a mutating operation (readOnlyHint false), and the description adds behavioral context about the privacy setting: boards are PUBLIC unless SECRET, and a Pin on a secret board is invisible to everyone. This goes beyond the annotations without contradicting them.

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?

Three concise sentences: purpose, usage trigger, and parameter guidance. Each sentence carries necessary information without fluff, and the key condition (empty board list) is front-loaded.

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 tool with three parameters and no output schema, the description covers the purpose, when to use it (with an alternative), and the critical privacy behavior. Nothing essential is missing for an agent to 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?

Schema covers 100% of parameters, so baseline is 3. The description adds extra meaning for the privacy parameter by explaining the implications of SECRET (invisibility) and advising to only use it if the user asks. This exceeds the schema's description.

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?

Description clearly states the tool creates a board on the connected Pinterest account, with a specific verb and resource. It also distinguishes from siblings by noting that a Pin cannot exist without a board and referencing list_pinterest_boards as the alternative to check.

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?

Explicitly tells when to use this tool: if list_pinterest_boards comes back empty, and not to tell the user you can't pin. It also warns about the SECRET privacy option and only to choose it if the user explicitly asks, providing clear when-not conditions.

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