cohere_embed

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

No annotations provided. Description fails to disclose key behavioral traits such as authentication requirements (api_key parameter not mentioned), rate limits, potential costs, or read-only nature. The verb 'create' implies mutation but no confirmation.

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?

Single sentence that is front-loaded and concise. However, some brevity could be sacrificed for clarity on usage and parameters.

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?

Lacks output schema and description does not hint at return format (e.g., vector dimensions). Incomplete for a 4-parameter embedding tool, especially without behavioral annotations.

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 coverage is 75%, but description adds no additional meaning beyond the schema. For example, it does not explain how to format the JSON array for 'texts' or the significance of 'input_type' enum values.

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?

Clearly states the action ('Create vector embeddings'), resource ('vector embeddings'), and provider ('Cohere's embed models'). Differentiates from sibling tools like cohere_chat and cohere_generate.

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?

No guidance on when to use this tool versus alternatives (e.g., cohere_rerank, cohere_classify). Misses opportunity to specify use cases like semantic search or clustering.

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