pinterest_list_boards

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Safe read' and 'paginated', which are valuable safety and behavior traits, but it doesn't cover auth requirements, rate limits, or output details beyond the board_id hint. This is adequate but not rich.

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 long, with the first sentence immediately stating the purpose and the second providing usage guidance. Every word earns its place, and it is front-loaded and easy to scan.

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 list tool with two optional params and no output schema, the description covers the core purpose, safety, pagination, and use case. It doesn't spell out the exact response fields, but the board_id reference gives enough context for an agent to infer the return shape.

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 the parameters (bookmark, page_size) are already fully described. The description adds no extra meaning to the parameters; it only repeats 'paginated' which is redundant. Baseline of 3 is appropriate when the schema does the heavy lifting.

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 'List the account's boards' with a specific verb and resource, distinguishing it from siblings like pinterest_get_board (singular) and pinterest_list_pins. It also mentions pagination, which is implied by the tool's name but reinforced in the description.

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 explicitly says 'Use before creating a pin to find the board_id you want to pin to — the create-pin call needs it', which gives a concrete when-to-use scenario. It doesn't explicitly state when not to use it, but the guidance is clear enough for an agent to decide between this and alternatives.

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