expand_concepts_batch

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

With no annotations, the description carries the full burden and does so well: it discloses per-item independent success/failure, idempotent retry semantics, and that canonical_concept collapses aliases while preserving aliases and provenance. The undefined limit behind 'bounded' is the only notable gap.

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?

Three tight sentences, each covering a distinct aspect (what it adds, canonical_concept behavior, failure/retry semantics), with the core action front-loaded. No filler.

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?

An output schema exists, so return values need not be described, and the description covers idempotency and per-item failure well. It is still incomplete on routing (batch vs singular sibling), the meaning of run_id, and what 'bounded' actually limits.

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 0% and neither required parameter is documented in the schema. The description meaningfully explains canonical_concept (an optional field not even named in the schema) and its effect on aliases/provenance, but leaves run_id and the structure of the concepts array entirely unexplained.

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 (add) and resource (a bounded batch of concept expansions), which distinguishes it reasonably from non-batch siblings. However, it never explicitly contrasts with the singular `expand_concepts` sibling, and the term 'host-agent concept expansions' is jargon that is not defined.

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 provides no when-to-use guidance, no exclusions, and no comparison to `expand_concepts` or any other sibling. The only operational hint is 'can be retried idempotently,' which is behavioral rather than a selection rule.

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