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

With no annotations, the description carries the full behavioral disclosure burden and does it well: it discloses approximate credit cost, per-result billing, no charge for empty or failed results, and the always-fresh default with an optional free cache hit. The phrase 'when scoped' is ambiguous about when board followers are included, preventing a perfect score.

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 compact, front-loaded with the resource and data fields, then cost and cache behavior. Each sentence earns its place, though the ambiguous 'when scoped' fragment and the dense credit-cost formulation keep it from being perfectly clean.

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?

There is no output schema, so the description should explain return values more fully; it lists key fields but leaves out the response envelope and when exactly board followers appear. Pagination, cursor, and limits are covered by the schema, but the missing clarification around 'scoped' leaves moderate gaps for an unfamiliar agent.

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 adds some value by tying the limit to per-result billing and emphasizing the cache cost, but it mostly restates cache behavior already documented in the schema. It contributes little beyond what an agent already gets from the parameter descriptions.

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 identifies the resource as 'Boards on a Pinterest profile' and enumerates returned fields, making it clear this is a profile-scoped listing tool rather than a single-board or pin-fetching tool. It is clear enough to be distinguished from siblings like pinterest_user_pins, though it does not explicitly name the alternatives.

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?

There is no explicit guidance about when to use this tool versus siblings such as pinterest_board, pinterest_search, or pinterest_user_pins. The intended use is only implied by the phrase 'Boards on a Pinterest profile', leaving the routing decision entirely to the agent.

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