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

The description goes beyond the readOnlyHint annotation by warning that the page is third-party content and must be treated as data, not instructions, and that prices or hours must never be invented. This is valuable behavioral guidance about external content and hallucination risk.

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?

Each sentence earns its place: audience, input/output, workflow, and safety warning. The content is front-loaded with the most important scoping information and stays reasonably compact despite covering multiple aspects.

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?

The single-parameter read-only tool is well covered: input, output, downstream usage, and hallucination guardrails are all described. A small gap is that candidate photos are not described in terms of format or how they should be handled, but this is minor for the stated workflow.

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?

With no schema description coverage, the description fully compensates by explaining what the url parameter should be: the address of a page the business already owns, with concrete examples such as a website, listing, or public profile. This adds real meaning beyond the bare uri format.

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 states a specific verb and resource: it takes a page URL and returns the page's readable text and candidate photos. This clearly differentiates it from tools like owner_setup by positioning it as the extraction step that feeds the setup call.

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?

It gives clear context: intended solely for business owners signed in to Awning, and placed in a workflow before a single owner_setup call. It does not explicitly name when not to use it or list alternative tools, but the ownership and workflow constraints are strong.

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