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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description adds value beyond that. It discloses pagination via cursor, the trim behavior with concrete size measurements (104KB vs 28KB), and the specific field subsets returned. This is rich behavioral context not covered by annotations.

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 dense and informative, but it is longer than strictly necessary. However, every sentence contributes value—function, pagination, field differences, size, trim, URL source, and alternative tool. It is front-loaded with the core purpose and structured logically, so the length is justified.

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 tool with 3 parameters, an output schema, and annotations covering safety, the description is exceptionally complete. It covers pagination, trim details, field subsets, URL construction, and the alternative tool. Nothing an agent needs to call it correctly is missing.

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?

Although schema coverage is 100%, the description adds significant meaning to each parameter: url is explained as a board URL (relative and needing prefix), trim is described with its effect on response size and retained fields, and cursor is tied to pagination. This goes well beyond the schema's simple field names and 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 states a specific verb ('Returns') and resource ('one page of pins from a board URL'), and explicitly differentiates from siblings like get_pinterest_search and get_pinterest_user_boards by mentioning the field subset differences and the alternative tool. An agent can immediately tell what this tool does and how it differs from others.

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 provides explicit guidance on when to use this tool: when you need pins from a specific board, and explicitly says to use get_pinterest_user_boards for a user's board list. It also explains where board URLs come from (search results or get_pinterest_user_boards) and how to handle relative URLs, which is critical for correct usage.

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