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

Annotations only cover readOnlyHint and openWorldHint, and the description goes well beyond them: it discloses the auth model (no API key, paid per request via x402), the batch ceiling (up to 100 inputs per call), the concrete cost ($0.143 USDC per call), and the response shape (matches OpenAI /v1/embeddings). Cost, auth and batch limits are exactly the behavioral facts an agent cannot get from structured fields.

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?

Purpose is front-loaded in the first sentence and the paragraph is dense with usable facts. There is mild redundancy in the pricing sentences ('flat price' followed by 'priced by size and model'), which slightly muddies the cost model, but overall little is wasted.

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?

There is no output schema, but the description compensates by stating the response shape is identical to OpenAI /v1/embeddings, and it covers auth, batch size, and cost. For a single-purpose, 100%-documented 3-parameter tool this is nearly complete, with only the 'flat price' vs 'priced by size' tension left unresolved.

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 100%, so all three parameters are already documented in the schema (including that `model` is ignored and `encoding_format` accepts base64). The description largely restates these facts rather than adding new syntax or format meaning, so the baseline of 3 applies.

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 first clause states a specific verb+resource: an 'OpenAI-compatible embeddings endpoint', with the backed model (bge-m3), dimensionality (1024) and language coverage (100+). It is clear what the tool does, but it never distinguishes itself from the sibling `embed` (or `vectors`/`rerank`), leaving the agent to guess which embedding tool to pick.

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?

Usage is implied through the integration mechanics ('point any OpenAI SDK at https://agents.citiviewgroup.com/v1') and the pricing model, so an agent understands how to call it. However, there is no explicit when-to-use guidance, no when-NOT-to-use exclusions, and no comparison against the clearly related `embed` sibling.

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