on_page_audit

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results come from the DataForSEO provider and lists the inspected elements, but says nothing about live fetching, latency, per-call cost, or failure behavior on unreachable pages.

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 core purpose is front-loaded in a single sentence with zero padding. The 'Args:' block and provider tag are minor boilerplate but carry real information, so little is wasted.

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 one-parameter read tool with annotations covering safety, the definition is nearly sufficient, but with no output schema the description should sketch what an audit returns (scores, findings, Pass/Fail items) so an agent knows what to expect. It also omits any note about analyzing one URL per call versus bulk.

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 0%, so the description carries the burden and does add meaning: it specifies 'Full URL' rather than a path or domain, and supplies a concrete example ('https://example.com/page') that clarifies scheme and format. It does not state whether redirects, query strings, or authenticated pages are accepted.

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 names a specific verb and resource ('Audit a specific page's on-page SEO') and enumerates the audited facets (title, meta, headings, content quality), which implicitly separates it from speed- or AEO-oriented siblings. It stops short of explicitly contrasting with page_speed_audit, so it is clear but not sibling-differentiating at the top level.

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?

Usage is only implied: an agent can infer this is the tool for evaluating a single page's on-page SEO elements. There is no explicit when-to-use statement, no exclusion of related audits (speed, AEO prompts), and no prerequisite or batching note for multiple URLs.

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