read_web_content

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds context about 'cache-first + API fallback behavior', which hints at performance characteristics and error handling, but doesn't cover critical aspects like authentication needs, rate limits, or what happens on failures. It's not misleading, but incomplete for a tool with potential network interactions.

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. There's no wasted text, but it could be slightly more structured by separating behavioral details. It's appropriately sized for a simple tool.

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 1 parameter with no schema descriptions, no annotations, and an output schema exists (which reduces the need to explain return values), the description is moderately complete. It covers the basic action and a behavioral trait, but lacks details on parameter usage, error cases, or integration with siblings, leaving room for improvement in guiding the 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 input schema has 1 parameter with 0% description coverage, so the schema provides no semantic details. The description adds minimal meaning by implying 'resource_id' is used to fetch 'complete record data', but doesn't explain the ID format, scope, or examples. It partially compensates for the low schema coverage but leaves significant gaps.

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 the tool 'fetch[es] complete record data by ID' which clarifies the verb (fetch) and resource (record data), but it's vague about what 'record data' refers to—web content, ads, or something else—and doesn't distinguish it from sibling tools like 'search_web_content' or 'read_ad'. It's not tautological, but lacks specificity for differentiation.

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 mentions 'cache-first + API fallback behavior', which implies a performance or reliability context, but provides no explicit guidance on when to use this tool versus alternatives like 'search_web_content' or other 'read_' tools. There's no mention of prerequisites, exclusions, or comparative use cases.

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