image_page_audit

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It goes well beyond a summary: it states it only fetches the provided URLs, involves no third-party service, returns a specific output shape, and explicitly instructs the agent to avoid speculation and to present results as interactive visualizations. This is strong transparency for a read-like audit tool.

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 long but well organized: purpose, audit scope, usage context, output summary, analysis guardrails, and presentation requirements. It is front-loaded with the core purpose. The list of audit factors and presentation instructions add length, but most sentences earn their place; a small amount of trimming could improve scannability.

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 there is no output schema and no annotations, the description handily covers what an agent needs: what the tool audits, what inputs to provide, where inputs should come from, what the output contains, and how results should be presented. The 'only fetch given URLs' and 'no third-party service' notes further reduce ambiguity for a network-fetching tool.

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 parameter names and defaults are fully documented. The description adds some context for fetch_metadata by listing EXIF/IPTC/XMP checks and implies max_images constraints, but it does not meaningfully elaborate on parameter semantics beyond the schema. The baseline of 3 is appropriate.

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 opens with a specific verb-resource pair: 'Fetches pages ... and audits every image on them.' It enumerates concrete audit dimensions, making the tool clearly distinct from siblings like image_impressions_no_clicks or content_gaps, which focus on impressions or content rather than per-page image SEO factors.

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 offers explicit context: 'Feed it URLs straight from image_impressions_no_clicks or image_search_quick_wins' and clarifies that it only uses URLs given, with no third-party service. It identifies the upstream use case clearly, though it does not explicitly state when not to use this tool versus other audit-style siblings like inspect_url or quick_wins.

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