aeo_well_known_url

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

With no annotations, the description carries the full burden. It states that no fetching occurs, indicating a non-destructive, read-only operation. However, it does not disclose potential errors, return format, or any side effects beyond the core behavior.

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 description is a single 11-word sentence with no redundancy or unnecessary words. It is maximally concise while conveying the essential purpose and constraint.

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 simple one-parameter tool, the description is nearly complete: it specifies input, action, and a key constraint (no fetch). It lacks detail on the output format or structure, which could be helpful since there is no output 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?

Schema description coverage is 0%, so the description must compensate. It mentions 'for an origin,' linking the parameter to the action, but does not explain what constitutes a valid origin (e.g., URI format, HTTPS required) or provide examples. The schema's format: uri is the only detail.

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 clearly states the tool computes the canonical AEO well-known URL for an origin without fetching. It specifies the action (compute) and resource (canonical AEO well-known URL), distinguishing it from other well-known URL tools like aup_well_known_url or agent_card_well_known_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?

The description mentions 'without fetching,' implying it should be used when no network request is wanted, but it does not explicitly state when to use this tool versus alternatives like aeo_fetch or other well-known URL tools. No comparison or exclusions are provided.

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