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

Annotations already establish readOnlyHint=true and openWorldHint=true, which the description does not contradict. Beyond that, it adds genuinely useful behavioral facts: a 100-text batch cap, fixed/flat pricing, and an explicit per-call cost under x402. It stops short of rate limits or truncation behavior for oversized inputs.

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?

Two dense sentences, front-loaded with capability, model, and dimensions, followed by limits and cost. The pricing sentence is somewhat redundant in restating price twice ('one flat price' then explicit token math and per-call USDC), which is the only slack.

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?

With no output schema, the description usefully discloses the output dimensionality (1024) and model, covering the main return-value question. The remaining gap is parameter selection between 'text' and 'texts' and any note on input size limits beyond count.

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%: 'texts' is documented ('Up to 100 texts') but 'text' is bare, and the description does not explain the relationship between the single-text and batch parameters. With zero required parameters, the description should clarify which one to pass and how they interact; the 100-text limit is the only added meaning, so the baseline 3 fits.

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?

States a concrete verb+resource: text embeddings for semantic search and RAG, with model identity (BGE-M3), dimensionality (1024), and multilingual support. However, it never differentiates itself from the near-identical sibling tool 'embeddings' (nor from 'vectors'/'rerank'), which is a real ambiguity given the catalog.

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?

Use cases ('semantic search and RAG') are implied, but there is no explicit when-to-use guidance and no mention of the sibling 'embeddings' tool that appears to do the same thing. An agent has no basis for choosing between embed, embeddings, vectors, or rerank.

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