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

The only behavioral disclosure is 'Page content is not stored.' With no annotations, the description does not mention network fetch behavior, potential errors, rate limits, or side effects, leaving most behavioral aspects undisclosed.

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 and front-loaded with the core purpose. It wastes no words, though it may be too terse to cover necessary context.

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 nine parameters, no output schema, and no annotations, the description omits essential context: what the return format is, which parameters are relevant to the stated purpose, whether parameters are optional, and how errors are handled. An agent cannot reliably invoke this tool based on the current description.

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 schema lists nine parameters with descriptions like 'Git ref name,' 'City name for a public weather hint,' and 'Search text' that are unrelated to the stated purpose of returning host, scheme, and HTTP status for a URL. The descriptions do not clarify how these parameters map to the tool's actual behavior.

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 action and output: 'Return host, scheme, and HTTP status for a URL.' However, it does not explicitly distinguish this from sibling tools like fetch-status or normalize-url, though the verb and resource are clear enough.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives, such as fetch-status or normalize-url, and gives no conditions or prerequisites.

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