resolve_styles

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

Discloses key behavioral trait of confidence levels due to no real DOM, which adds context beyond a simple read. No annotations exist, so description carries full burden; it sufficiently addresses limitations.

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?

Two efficient sentences with no superfluous information. First sentence states core purpose, second adds usage guidance and behavioral nuance. Front-loaded and to the point.

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?

Given tool complexity (CSS cascade) and no output schema, description outlines expected return values (properties, winner, overridden, confidence). Sufficient for an agent to gauge use, though could mention error handling or file discovery behavior.

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 100%, so description adds minimal new semantics beyond schema. The description reinforces the overall behavior but does not enhance parameter understanding beyond what schema provides.

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?

The description clearly states the tool resolves CSS for a given selector, listing specific outputs (properties, winning rule, overridden rules) and distinguishes from sibling 'trace_property' by focusing on full cascade context.

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?

Explicitly advises calling this before modifying styles to understand cascade context, providing clear usage guidance. Does not mention alternatives explicitly but implies it for initial diagnosis.

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