Board

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

Goes beyond annotations by disclosing that the call consumes paid API credits, requires confirm=true, and clarifies that the read-like POST does not publish to social platforms — directly addressing the readOnlyHint=false signal. Missing rate-limit or retry behavior keeps it from a 5.

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?

Two dense sentences, front-loaded with the primary action and return fields, then the credit/confirm constraint. No wasted text, though the return-field enumeration is long.

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?

With no output schema, the description usefully enumerates the returned fields and covers the credit cost and confirm requirement. Gaps remain around the account parameter and pagination termination, but the tool is callable correctly from what is given.

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 100%, so the baseline is 3. The description only lightly reinforces cursor (next page) and trim (lighter response) without adding syntax or default behavior beyond the schema, and says nothing about the account credential parameter.

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?

Specific verb+resource+scope: fetches a paginated list of pins from a Pinterest board by URL, and enumerates returned fields. It is clearly distinguishable from siblings like pinterest_pin (single pin) and pinterest_user_boards (boards of a user).

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 states the pagination mechanism (cursor) and the trim option, and warns that confirm=true is required, which implies when the call is valid. But it never compares this tool against siblings such as pinterest_search or pinterest_pin, nor states when a board fetch is preferred.

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