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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond that: it discloses the return shape ('evidence-based score with per-dimension findings') and an auth fact ('No API key required'). It does not mention runtime, rate limits, or failure modes for unreachable URLs.

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?

Three short sentences, zero waste, with the core purpose front-loaded and the output/auth notes kept to the tail. Nothing is padded or restated.

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?

With no output schema, the description carries the burden of describing the return value and does so ('score with per-dimension findings'). A single required param is documented in the schema. Only minor gaps remain, such as expected latency of a scan and whether the score is deterministic.

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% and there is only one required parameter, so the schema fully documents 'url' including its absolute-URL format. The description adds no syntax, format, or constraint detail beyond the word 'website', so the baseline of 3 applies.

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 and resource: 'Audit a website's AI-search (GEO/AEO) readiness'. This is clearly distinguishable from the sibling list_*/get_* tools, which enumerate stored resources rather than performing an analysis against an input URL.

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 implied by the verb ('audit a website') but there is no explicit when-to-use framing, no prerequisite conditions, and no named alternatives among the omniforce siblings. 'No API key required' hints at context but is not usage guidance.

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