quipu_embed_backfill_graph

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds real value by narrowing the blast radius ('does not rewrite ROOT entity text'), but never says what does get overwritten, whether existing embeddings are replaced or skipped, or what cost/rate limits apply.

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?

A single front-loaded sentence with zero filler, and the exclusion clause is placed where it is most useful. It is slightly cryptic — 'ROOT entity text' is never defined — but nothing 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?

For a destructive, open-world mutation with no output schema and no documented parameters, the description is too thin. It omits idempotency/resumability, what a backfill call returns, and any indication of side effects beyond the ROOT exclusion, which an agent needs before triggering it.

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 0%, so the description must carry the load. It does map loosely onto both params ('named-graph' → graph, 'bounded number' → max_entities), but gives no format for the graph identifier and no default or upper bound for max_entities, so an agent still guesses at valid values.

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?

States a specific verb (backfill), a specific resource (named-graph entity embeddings), and a scope constraint (a bounded number). The 'named-graph' qualifier implicitly separates it from the sibling quipu_embed_backfill, though that sibling is never named explicitly.

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?

There is no guidance on when to choose this over quipu_embed_backfill, no prerequisites (graph must exist / be unfrozen), and no advice on how to size max_entities. 'Bounded number' hints at incremental batching but leaves the operator to infer it.

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