pinterest_ingest

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

With no annotations, the description carries full burden. It discloses a key side effect: on first run, ChromaDB downloads a ~90 MB embedding model. However, it omits other behaviors like whether storage is additive or destructive, idempotency, or network requirements. The disclosed behavior is valuable but not exhaustive.

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 extremely concise: three sentences total, with the core purpose in the first sentence. The note about the model download is placed after the purpose but is critical. The bullet-style args are clear and avoid fluff. Every sentence 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?

Given the tool's simplicity (2 params, no nested objects) and the existence of an output schema (described as 'has output schema: true'), the description covers the main functional aspects: what it does, what it takes, and a key behavioral note. It lacks details on storage semantics (e.g., deduplication, overwrite behavior) but is largely sufficient for an agent to use it 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?

Schema description coverage is 0%, so the description must compensate. It explains 'analyses' as output from pinterest_analyze and 'query' as optional label. This adds meaning beyond the schema (which shows only types and required status) but lacks detail on the expected structure of analyses (e.g., exact fields) or query format.

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 clearly states the tool stores visual analyses in ChromaDB for future semantic retrieval, distinguishing it from sibling tools like pinterest_analyze (analysis) and visual_search (search). The verb 'store' is specific, and the resource 'ChromaDB vector base' is well-defined, with input tied to pinterest_analyze output.

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 after pinterest_analyze (by specifying 'output list from pinterest_analyze') but does not explicitly state when to use or not use this tool versus alternatives. There is no guidance on prerequisites or when to skip this step, leaving the agent to infer context from sibling tool names.

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