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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the tool 'returns' outputs but doesn't describe what happens during rendering (e.g., page loading, timeout behavior, error handling), whether it's idempotent, or any rate limits. The description adds minimal context beyond the basic operation, leaving significant behavioral gaps for a tool with 8 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 a single, efficient sentence that front-loads the core purpose and key output options. It avoids redundancy and wastes no words, though it could be slightly more structured by separating purpose from usage guidance. Every part earns its place, making it highly concise.

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's complexity (8 parameters, no output schema, no annotations), the description is minimally complete. It covers the basic operation and output types but lacks details on error conditions, performance characteristics, or example usage. Without annotations or output schema, more behavioral context would be helpful, but it's adequate for a starting point.

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 schema already documents all parameters thoroughly. The description adds marginal value by hinting at the relationship between 'full_page' and cache URL preference, but doesn't provide additional syntax, format details, or usage examples beyond what the schema specifies. This meets the baseline for high schema coverage.

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's purpose: 'Renders a screenshot of a website' with the specific verb 'renders' and resource 'website screenshot'. It distinguishes the output options (image or JSON with cache URL) but doesn't need sibling differentiation since no sibling tools exist. The purpose is specific and unambiguous.

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 provides implied usage guidance by mentioning 'preferred for full-page screenshots' for the cache URL option, suggesting when to choose JSON over image output. However, it lacks explicit when/when-not instructions or alternatives, and doesn't address prerequisites like network access or authentication needs. With no sibling tools, this is adequate but not comprehensive.

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