get_vector

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

No annotations; description discloses cold-vector omission and not_found errors, adding useful behavioral context. However, parameter-schema mismatch contradicts described functionality.

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 sentences, somewhat concise, but first sentence is awkwardly phrased with a colon. Could be more structured.

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?

No output schema, no parameters in schema; description covers behavior but is incomplete due to missing parameter definitions, making the tool effectively undefined.

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 has zero parameters, but description assumes id and include_values. With 100% schema coverage (trivially) and no params, description fails to provide meaning and contradicts schema.

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?

Description clearly states it fetches a single vector by id and returns id/metadata/optional embedding, distinguishing it from siblings. However, the input schema lacks parameters for id and include_values, creating a critical mismatch that undermines clarity.

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 fetching a single vector and explains behavior for cold vectors, but no explicit when-not or alternatives to sibling tools.

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