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

With no annotations, the description carries the full burden. It discloses the read-only nature ('Check'), the temporal scope (current billing period), and the returned fields, but says nothing about auth requirements, rate limits, or whether usage is real-time.

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 short sentences, front-loaded with the action and scope, followed by the concrete return content. No waste.

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 zero-parameter read-only tool with no output schema, the description is largely complete: it explains what is queried and what is returned. Minor gap is lack of auth/real-time context, but nothing needed to invoke it correctly is missing.

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?

Zero parameters, so there is nothing to document; baseline is 4. The description correctly requires no input, matching the empty 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 (check) and resource (API usage) plus the scope (current billing period) and what is shown (screenshots used, remaining, limits). It is unambiguous what it does, though it does not explicitly name or distinguish itself from the sibling take_screenshot.

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?

Usage is implied by 'current billing period' — the agent infers this is a read-only status check. There is no explicit statement of when to use it, no exclusions, and no mention of the sibling, so guidance is implied rather than stated.

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

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the result is base64-encoded image data and mentions several feature areas, but it does not disclose important behavioral traits such as permissions, rate limits, timeout behavior, or the fact that custom JS and click actions can affect the target page.

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 short and front-loads the core action and return format. The phrase 'and more' is slightly vague, but overall the structure is efficient and appropriately sized for a tool whose parameter details are covered by the schema.

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 an 18-parameter tool with no annotations and no output schema, the description is adequate but not fully complete. It explains the return value and major capabilities, but it does not cover behavioral context such as side effects from JS execution, rate limits, or error conditions.

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 the input schema already documents all 18 parameters, including url, viewport, format, and selectors. The description highlights a subset of capabilities such as viewport sizes, device emulation, dark mode, and full-page capture, but adds no syntax or format detail beyond what the 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 states a specific verb and resource: 'Capture a screenshot of any webpage.' It also clarifies the return format as base64-encoded image data. The purpose is unambiguous and distinct from the unrelated sibling check_usage.

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?

The description implies usage by saying it captures 'any webpage' and listing supported features, but it gives no explicit when-to-use guidance, prerequisites, or exclusions. Since the only sibling is check_usage, there is no alternative screenshot tool to compare against, but the guidance remains implied rather than stated.

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