pinterest_autocomplete

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It merely states the function and gives no hints about return format, rate limits, authentication, or edge cases. The description's 'Get' is implicit from the tool name, adding no extra transparency.

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, front-loaded sentence of 10 words. Every word contributes meaning, with no filler or redundancy.

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 simple tool with two parameters and no output schema, the description gives a bare-minimum overview. It does not mention the return value structure (e.g., an array of strings), nor any limitations. It is adequate but leaves clear gaps that could confuse an 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 50%; the 'term' parameter has a description with an example, while 'limit' has only type/default/min/max. The tool description adds a bit of context by calling it a 'partial query' but does not explain the role of 'limit' or the interplay between parameters. Overall, the schema provides adequate parameter semantics.

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 uses a specific verb ('Get') and names the resource ('Pinterest search-term suggestions') with a clear qualifier ('for a partial query'). It clearly distinguishes from siblings like pinterest_search, which would return full search results.

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 with a partial query but does not explicitly state when to use this tool instead of alternatives, nor does it mention exclusions or comparisons to sibling tools like pinterest_search. The context is clear but not explicitly guided.

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