style

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

With no annotations, the description carries the full burden. It does add real behavioral context: null removes a property, and group application with child inheritance/override semantics. However, it says nothing about the mutation's concurrency/versioning behavior (expected_revision) or whether changes are undoable.

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, front-loaded with the core purpose and an example, with no filler. The parenthetical aside about inheritance is the only place where information is compressed at the cost of immediate readability.

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, no output schema, and a nested props object, this is reasonably but not fully complete. The core props semantics are covered, yet two of four parameters and the concurrency contract remain unexplained.

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% across 4 parameters, so the description must compensate. It explains the semantics of 'props' (CSS property names, null meaning removal) well, but leaves 'ids', 'show', and 'expected_revision' entirely undocumented in both description and schema.

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 CSS style properties on objects,' with an inline example showing the props shape. It is clear what the tool does, but it does not distinguish itself from close siblings like 'attributes' or 'text', which an agent may reasonably confuse with it.

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?

No when-to-use guidance and no named alternatives, despite several plausible overlapping siblings (attributes, text, inspect). The only conditional advice is diagnostic ('inspect them if a colour does not take'), which is troubleshooting, not selection guidance.

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