describe_shadow

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

Describes return structure (JSON with light and shadow arrays) and notes it works for open shadow roots. No annotations provided, but the description covers what to expect. Lacks mention of performance or limitations, but for a read-only tool this is adequate.

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 sentences, well-structured with main purpose first. No fluff, uses clear examples and references to sibling tools. Very efficient.

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?

Covers output format, use cases, and relationship to other tools. Lacks parameter details but provides enough context for a debugging tool. No output schema, but description explains return shape adequately.

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 description must add meaning. It mentions selector implicitly but does not describe its format or required usage. The max_depth parameter is not mentioned at all, leaving a gap for the agent.

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?

Clearly states it dumps a custom element's nested shadow-DOM tree for debugging. Describes output format (condensed JSON with tag, id, role, etc.) and distinguishes from siblings (find_buttons/find_inputs).

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 says when to use: when find_buttons/find_inputs aren't surfacing a control. Provides guidance on using result to target click_shadow or chain queries. No explicit when-not-to-use but context is helpful.

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