quipu_embed_backfill

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is largely covered. The description usefully adds that the call consumes external embedding resources (cost/latency) and persists vectors (side effect with no undo), but says nothing about idempotency, resumability, or scope of what is overwritten.

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 short sentences, front-loaded with the action and target, followed by the operational caveats. Every clause adds information: provider source, external resource consumption, and vector persistence.

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 parameters, no output schema, and annotations carrying the safety profile, the description supplies enough to call it correctly: what it fills, with what, and that it costs external resources and writes vectors. Only the choice against quipu_embed_backfill_graph and any run-length/idempotency expectations are left open.

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 tool takes zero parameters, so there are no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misrepresents or omits parameter behavior.

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 names a specific verb (backfill) and resource (missing ROOT entity embeddings) plus the mechanism (configured provider). The 'ROOT entity' scoping implicitly separates it from the sibling quipu_embed_backfill_graph, but the sibling is never named, leaving the agent to infer the distinction.

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 only implied by 'missing' embeddings – run it when embeddings are absent. There is no explicit when-to-use, when-not-to-use, or routing guidance relative to quipu_embed_backfill_graph, which is the obvious alternative for a backfill task.

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