page_technical_audit

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

With no annotations, the description carries the burden and does it well: it discloses that the fetch uses follow_redirects=False for SSRF safety, that /robots.txt is also retrieved, that no auth or Google API calls occur, and the possible verdicts (healthy | issues_found | fetch_error). Remaining gaps like rate limits or exact fetch timeouts are minor.

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?

Front-loaded with the one-line purpose, then a scannable list of checks, then constraints and verdicts. Every line is informative, though the multi-line check inventory is longer than strictly necessary for an agent that mainly needs scope and routing.

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?

An output schema exists, so return values needn't be explained, yet the description still surfaces the verdict vocabulary. Combined with the check list, SSRF behavior, auth requirements and redirect handling, an agent has everything needed to invoke it correctly without opening the schema.

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?

Only one parameter with 0% schema description coverage, so the description must compensate and largely does: it clarifies the url should be the final canonical URL when behind redirects, and implicitly frames it as an absolute page URL given the SSRF/redirect notes. Enum/failure-mode detail for malformed URLs is not covered.

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 (audit) and resource (on-page technical SEO) and enumerates exactly what is checked: meta tags, canonical, robots.txt, security headers, redirects, Googlebot blocking. This clearly separates it from siblings like inspect_url, pagespeed_audit, heading_audit and schema_validate.

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?

Gives a concrete usage condition ('For pages behind redirects, supply the final canonical URL directly') and contextual constraints ('No Google API calls. No authentication required'). It stops short of explicitly naming alternative tools for overlapping checks (e.g. inspect_url), but the domain is narrow enough that routing is inferable.

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