memo_embed_batch

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. The description adds 'Read-only' and clarifies that an empty input returns no vectors without error. This adds useful behavioral context beyond annotations, with no contradictions.

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 concise: three sentences front-loaded with the main action. No extraneous text. Every sentence 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?

Given the low complexity (1 parameter), presence of an output schema, and rich annotations, the description fully covers purpose, usage, and key behavioral details (empty input). No gaps.

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?

The single parameter 'texts' is described as 'a list of strings' and 'document strings,' but the schema has no property descriptions (0% coverage). The description adds minimal meaning beyond the schema, not fully compensating for the lack of schema details. It could clarify what constitutes a document string.

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 or more document strings using memo's document embedder. It distinguishes itself from siblings like memo_embed_query (query embedding) and memo_get_embedder_profile (model info) by being a batch operation for diagnostics or external indexing.

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 specifies to use for diagnostics or external indexing when document vectors from the same internal model are needed. It does not explicitly state when not to use or list alternatives, but provides clear context and notes edge-case behavior (empty list).

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