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

Annotations already cover the safety profile (readOnly, idempotent, closed-world). The description adds genuinely useful context beyond them: the returned data is synthetic and it mirrors the exact field set of the paid audit, which stops an agent from treating the output as a real audit result.

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?

One sentence, front-loaded with the action and resource, with the two qualifiers (fictional page, full field parity with the paid audit) appended efficiently. Nothing 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?

With no output schema, the description's promise of 'every field the paid audit returns' is the main signal about the return value, which is adequate for a zero-argument sample tool. It could say more about format or size, but nothing needed to invoke it correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is required by describing a canned sample, and there are no parameters for it to document.

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 (returns an example audit report) and adds the key qualifier that the page is fictional. It implicitly differentiates from audit_landing_page by being the sample/free variant, but never names the siblings, so an agent must infer the distinction from context rather than being told.

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 word 'example' and 'fictional page' imply this is for inspecting the report shape rather than auditing a real page, but the description never states when to choose it over audit_landing_page or preview_landing_page. Usage is left to inference.

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