set_equations

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses ordering semantics ('in order, later ones may use earlier ones'), atomic rollback ('a refused equation undoes the whole list'), and return contents per equation. It omits permission requirements and what exactly triggers a refusal, but the core mutation behavior is clearly conveyed.

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 short sentences, front-loaded with the purpose. Each sentence adds distinct value: purpose/rebuild behavior, ordering/atomicity, and return contents. 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?

For a batch mutation tool with no annotations and no output schema, the description covers atomicity, ordering, and return values reasonably well. However, it does not explain the equation item format (critical given 0% parameter coverage) or any prerequisites such as an active document or required permissions, leaving gaps an agent must guess at.

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 schema has one parameter with 0% description coverage and an empty item type ({}). The description only says 'list of equations' and 'As set_equation for each,' which does not explain the item format, required fields, or how each equation is represented. For a single undocumented parameter, this leaves significant ambiguity.

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 and resource ('Add or replace a list of equations at once'), plus the distinctive batch behavior ('with one rebuild at the end'). This clearly distinguishes it from the single-equation sibling set_equation and from list_equations/delete_equation.

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?

Implies batch use through 'at once' and 'one rebuild at the end,' and references set_equation as the per-item equivalent. It does not explicitly state when to prefer this over repeatedly calling set_equation, but the context is clear enough for an agent to choose the batch tool.

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