embed_text

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

No annotations exist, so description carries the burden. It discloses paid cost (~$0.0003 in KAS) and a limit of 64 texts. However, it does not mention that the operation is stateless, read-only, or any side effects, which is adequate but not thorough.

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 with no fluff, covering key aspects: action, limit, model, dimensions, cost. Every word adds value.

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 tool with no output schema, the description covers purpose, limit, model, and cost. Missing return format (e.g., 2D array of floats) but otherwise complete enough.

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?

With 0% schema description coverage, the description adds meaning by specifying the limit (up to 64 texts) and the output characteristics (768-dim, nomic-embed-text). It does not describe input constraints like text length or 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 specifies the verb 'embed' and resource 'texts', with details about dimensionality (768-dim) and model (nomic-embed-text). This distinguishes it from sibling tools like classify or 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?

Implies use for embedding text with a limit of 64 texts and a cost, but no explicit when-to-use or alternatives among siblings. The paid nature is a usage hint but not comparative.

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