attributes

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

With no annotations, the description carries the full burden, and it does disclose one non-obvious behavior: passing null removes the attribute. It does not explain overwrite behavior for existing values, what happens on a revision mismatch (relevant given expected_revision), or whether this mutates multiple elements at once.

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 that wastes nothing, with the core action leading and the removal semantics immediately after. The trailing ellipsis in the example list is slightly loose but signals that the list is illustrative.

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 mutation tool with no annotations and 0% parameter description coverage, the definition leaves too much unstated: the meaning of ids and expected_revision, overwrite/conflict behavior, and multi-element semantics. An output schema exists, so return values need not be described, but the input side is materially under-documented.

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%, so the description must compensate, and it only partially does: the null-equals-remove semantics for 'attrs' values and example attribute keys are genuinely helpful. But 'ids' (which identifiers? element ids? comma-separated?) and 'expected_revision' (presumably an optimistic-concurrency token) are entirely unexplained in both schema and description.

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+resource ('Set ... XML attributes') with concrete attribute-name examples (inkscape:label, width, rx, xlink:href, id), which makes it distinguishable from siblings like style, text, and structure. It does not explicitly contrast itself with those siblings, so it falls short of a 5.

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 parenthetical '(or with null, remove)' tells the agent how to perform a deletion, which is real usage guidance. However, it never says when to use attributes versus style (CSS properties) or structure, nor does it mention any prerequisites, so usage is only implied.

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