capture_public_ad_page

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does disclose that it operates only on 'allowlisted public' pages and does not attempt login or bypass, which is useful safety context. However, it doesn't state whether the operation is idempotent, what happens if the URL is not allowlisted, whether it overwrites existing stored data, or any error behavior. It also doesn't mention that it stores data (a write operation) with potential implications. These gaps reduce transparency.

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, compact sentence that front-loads the core action and constraints. It is free of filler and every clause carries meaning: it specifies what is fetched/stored, the source domain, and the negative constraint. This is exemplary conciseness.

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 tool with three parameters, no output schema, and no annotations, the description provides the core function but lacks important contextual details. It does not explain what the tool returns (the stored result or a confirmation), how it handles failures (e.g., if the URL is not public or allowlisted), or when an agent should prefer this over a sibling like record_ad_swipe. Given the lack of annotations and output schema, the description is not fully sufficient for an agent to decide when and how to use it correctly.

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 all three parameters (url, timeout_ms, max_text_chars) already have descriptions in the schema. The tool description adds little beyond the schema: it mentions 'fetch and store' and 'allowlisted public' but these are already implied by the schema's url description. There is no additional clarification about how parameters interact or edge cases, so the description adds minimal value beyond the structured 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?

The description clearly states the tool's function: 'Fetch and store metadata/text from an allowlisted public ad-library page'. It names the specific verb ('Fetch and store'), the resource ('allowlisted public ad-library page'), and explicitly notes what it does NOT do ('without login or bypass behavior'). This distinguishes it from siblings like build_meta_ad_library_url (which builds URLs) and record_ad_swipe (which records swipes), making it easy for an agent to understand its core role.

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 gives context about the intended use: it is for 'allowlisted public ad-library pages' and avoids 'login or bypass behavior'. However, it does not explicitly name alternative tools or state when to use this tool versus siblings. For example, it doesn't mention that record_ad_swipe is for user swipes, or when to use build_meta_ad_library_url to construct a URL first. The usage guidance is implied but not explicit, leaving the agent to infer appropriate conditions.

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