pinterest_create_board

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

With no annotations, the description carries full burden. It discloses live visibility ('Live, immediately visible on the profile if privacy=PUBLIC'), authorization requirements ('agent_id must hold social'), and failure conditions ('or the call is refused'). These go far beyond the schema and give the agent critical behavioral expectations.

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 two sentences, front-loaded with the primary purpose, and includes only high-value details about visibility, prerequisites, and failure. No waste.

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 5-parameter tool with no annotations or output schema, it covers purpose, prerequisites, side effects, and refusal behavior. It does not mention the return value, but given the lack of output schema, this is a minor gap rather than a critical omission.

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 coverage is 100%, so baseline is 3. The description adds meaning for agent_id by specifying it must hold 'social' permission, and clarifies the consequence of task_id requirements. It does not repeat all parameters but enriches two key ones.

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 new Pinterest board on the account.' This clearly distinguishes it from sibling tools like pinterest_create_pin, and the read-only tools (get/list). No ambiguity about what the tool does.

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?

It provides clear context for when to use the tool by stating prerequisites: 'Requires agent_id (must hold 'social') and task_id (task must be cleared for the with_nate brand — Done and carrying an approved output).' It does not explicitly name alternatives or exclusion criteria, but the purpose and requirements make usage obvious.

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