pinterest_search

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. However, it only states the basic action without revealing key traits such as browser automation (implied by the headless parameter), result format, pagination, or any potential side effects. This minimal transparency is insufficient for agents to understand the tool's operational behavior.

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, focused sentence that efficiently communicates the core purpose without any extraneous words. It is appropriately sized and front-loaded, making it quick for an agent to parse.

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?

Given the lack of output schema and annotations, the description is insufficiently complete for a search tool. It does not specify return values (e.g., image URLs, metadata), result sorting, error handling, or rate limits. The description omits critical operational context that an agent would need to use the tool correctly.

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?

All three parameters (keyword, limit, headless) are fully described in the input schema with 100% coverage. The description adds no additional meaning beyond the schema; for example, 'by keyword' merely repeats the required parameter. Per guidelines, with high schema coverage, baseline score is 3.

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 'Search for images on Pinterest by keyword' clearly states the action (search), resource (images on Pinterest), and method (by keyword). It effectively distinguishes this tool from its siblings: 'pinterest_get_image_info' retrieves details of specific images, while 'pinterest_search_and_download' implies additional download functionality, making this tool's purpose unique.

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 provides no guidance on when to use this tool versus its siblings or alternatives. It lacks information about prerequisites, limitations, or appropriate contexts, leaving the agent to infer usage from the tool name alone.

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