snapshot

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

With no annotations and a single-sentence description, there is no disclosure of behavioral traits such as whether the command is destructive, its runtime implications, or what the returned data contains. This is a significant gap for a tool with many parameters.

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?

The description is overly terse (one sentence) and lacks structure. While brevity is valued, this is underspecification, not conciseness. It does not provide enough information to justify its length.

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 the tool has 24 parameters, no output schema, and no annotations, the description is grossly inadequate. It fails to provide any context about the tool's behavior, return value, or how parameters interact, making it nearly useless for an agent.

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 description coverage is 75%, but the tool description adds no additional meaning for parameters like 'compact', 'depth', 'scope', etc. It fails to explain their effect in the context of an accessibility snapshot, leaving the agent without crucial context.

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 states a specific verb ('Capture') and resource ('accessibility snapshot'), clearly indicating the tool's function. However, it does not differentiate from the sibling 'screenshot' tool, which could be ambiguous for an agent.

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 guidance is provided on when to use this tool versus alternatives like 'screenshot' or 'diff'. The description lacks any context about prerequisites or typical scenarios.

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