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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond that: the return shape (base64 bytes AND a persisted file_id), where the file lives (DialogBrain files storage), and the anti-pattern to avoid (re-calling files.upload). That is genuinely useful behavioral disclosure.

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?

Front-loads purpose, then output shape, then workflow, then the usage constraint. Three tight sentences with no filler; every clause carries distinct information.

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?

No output schema exists, so the description rightly explains return values and persistence, and annotations cover safety. The main gap is parameter coverage — the effect of inline_bytes and full_page is left unstated, which matters for an agent deciding how to call it.

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 only 20%, so the description should compensate but does not. It never explains ref, page_id, full_page, or inline_bytes — notably inline_bytes, which gates whether the advertised 'base64-encoded image bytes' are even returned. The one parameter with schema help (in_workspace) is untouched by the 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 ('Capture a PNG screenshot') and scope ('of the page or a specific element'). It explicitly differentiates from the sibling browser_snapshot, so an agent can pick between them without opening a schema.

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?

Gives an explicit when-not and alternative: 'Use sparingly — favor browser.snapshot for structured DOM understanding.' It also routes the downstream workflow (pass file_id to messages.send, do not re-upload), leaving nothing to inference.

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