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

With no annotations, the description must carry the full burden of behavioral disclosure. It only mentions that query and fragment are dropped, which is a start. It does not explain what happens with invalid URLs, whether it fetches the URL, how it handles the other parameters (e.g., city, feed, json) that are present in the schema, or what the output format looks like. This is a significant gap.

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 very concise: a single sentence. That is positive for conciseness. However, for a tool with 9 parameters and no annotations, the brevity becomes under-specification rather than efficiency. It is front-loaded with the core action, but it lacks the structure needed to clarify the tool's full behavior.

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?

Given the tool has 9 parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain the purpose of the extra parameters, the output format, error behavior, or how the tool handles different input types. An agent cannot reliably call this tool correctly based on the description alone.

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%, so the baseline is 3, but the description adds no value beyond the schema. It does not identify which parameter is the primary URL input (likely 'url'), nor does it clarify how the other parameters relate to the stated purpose. The schema itself has descriptions like 'City name for a public weather hint; discarded after the call,' which are confusing and not tied to URL normalization. The description fails to resolve this confusion.

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 clear action: 'Return origin, host, and path for a URL. Query and fragment are dropped.' This is specific and names a resource. However, the input schema includes 9 unrelated parameters (city, feed, json, zone, etc.) that are not explained in the description, creating ambiguity about the tool's true scope. It does not differentiate from sibling URL tools like browser-url-ok or figma-url-shape.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention conditions, exclusions, or which sibling tools it competes with. An agent would have to infer usage from the name and description alone, which is insufficient given the sibling list includes several URL-related tools.

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