list_pinterest_boards

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

No annotations are provided, so the description bears full responsibility. It only states the basic operation ('List...') without disclosing authentication requirements, read-only nature, pagination behavior, or any side effects. The description adds minimal value beyond the function name.

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 a single concise sentence with no redundancy. While it could be slightly more informative, it is appropriately sized for a simple list operation.

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 4 parameters, lack of output schema, and absence of annotations, the description is incomplete. It does not explain the return format, pagination, authentication method, or filtering by privacy. A more comprehensive description is needed for effective tool use.

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 description coverage is 75% (3 of 4 parameters have descriptions). The tool description adds no additional meaning beyond the schema; it does not clarify page_size or the implications of privacy. Baseline 3 is appropriate since schema does most of the work.

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 'List Pinterest boards for the authenticated user' clearly states the verb (List), resource (Pinterest boards), and scope (authenticated user). It distinguishes itself from siblings like get_pinterest_board (specific board), list_pinterest_pins (pins), and create_pinterest_pin (creation).

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 implies usage for listing all boards but provides no explicit guidance on when to use this tool versus alternatives like get_pinterest_board for a single board. No exclusion criteria or context is given.

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