memo_embed_query

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description reinforces 'Read-only' and adds useful behavioral details: rejects empty text, and returns vector, dimension, and model id. No contradictions, but the description mainly confirms annotations with small additions, so a 4 is appropriate.

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?

The description is three short sentences that front-load the core purpose, then add usage context and return behavior. Every sentence adds value, with no wasted words. It is highly compact yet informative.

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?

Given a simple tool with one parameter and an existing output schema, the description covers all necessary aspects: purpose, usage context, parameter semantics, and return value structure (vector, dimension, model id). It is fully sufficient for an agent to use correctly.

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 100% with a single parameter 'text'. The description for this parameter adds key context: 'instruction-prefixed for asymmetric retrieval' and clarifies that empty/whitespace-only input raises an error. This meaningfully extends beyond the schema's basic type description.

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 states the tool embeds one query string using memo's query embedding path, and specifies it's for diagnostics or integrations needing the exact vector for retrieval queries. This verb+resource+scope is specific and distinguishes it from sibling tools like memo_embed_batch.

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?

The description explicitly says 'Read-only' and 'Use for diagnostics or integrations that need the exact vector memo would use for retrieval queries.' It also notes that empty text is rejected. However, it does not mention alternatives (e.g., memo_embed_batch for batch processing) or when not to use it, which would improve clarity.

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