list_boards

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'List your Pinterest boards', which implies a read operation but does not explicitly state it is non-destructive, whether authentication is required, or what the response contains. Minimal disclosure beyond the bare action.

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 extremely concise, with two short sentences and no filler. The primary action is front-loaded, and the parameter value list is provided efficiently. It is appropriately sized for a simple tool.

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?

Given the tool's simplicity (one optional parameter, an output schema present, no annotations), the description covers the essential purpose and parameter values. It doesn't mention pagination or authentication, but for a straightforward list operation, it is sufficiently complete. The presence of an output schema reduces the need to describe return values.

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 compensates for the 0% schema description coverage by listing the allowed values for the privacy parameter (ALL, PUBLIC, SECRET). This adds meaning beyond the schema, which only specifies a string default. However, it doesn't explain what each value does or the effect of filtering, so it's not fully comprehensive.

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 states a specific verb ('List') and resource ('your Pinterest boards'), making the tool's purpose immediately clear. It is distinct from sibling tools like create_board or get_board_pins, and the addition of the privacy parameter values further clarifies its 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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention context like 'to view all boards' or 'when you need a list of boards', and there is no comparison to sibling tools. The privacy parameter hint is present but doesn't address usage context.

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