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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and openness profile is covered without the description's help. The description adds the result composition (title, description, image, board, pinner), which is useful but does not disclose pagination, rate limits, auth needs, or other behavioral traits beyond the 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?

A single front-loaded sentence that names the resource and lists the returned fields with zero wasted words. It is efficiently sized for a simple search tool, though its brevity comes at the cost of omitting other guidance.

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 single-parameter read-only search, the description plus annotations cover enough to invoke the tool, and the presence of an output schema means return values need not be detailed. However, the query parameter's expected content is missing, and there is no usage context, so the definition is only minimally complete.

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 0% for the single required 'query' parameter, so the schema provides no semantics at all. The description says 'pin search' but never explains what the query string should contain — keywords, a URL, a username, etc. — leaving the only input essentially undocumented.

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?

States a specific verb and resource ('Pinterest pin search') and enumerates the fields returned for each match. It is clear what the tool does, but it never names or contrasts the sibling tools like pinterest_pin or pinterest_user_pins that also surface pins, leaving differentiation to inference from tool names.

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 gives no when-to-use, when-not-to-use, or alternative guidance. An agent could infer from 'search' that this is for query-based pin discovery, but nothing routes it against pinterest_pin or pinterest_board.

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