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

With no annotations provided, the description must carry the full burden of behavioral disclosure, but it reveals nothing beyond being a 'catalog'. It doesn't state whether the tool is read-only, what it returns, how inputs are used, or what side effects occur. The schema hints at shape checks, but the description doesn't confirm any behavior, making it highly opaque.

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 short sentence, which is efficient in length but under-specifies entirely. It lacks any structure that front-loads purpose or usage, and its brevity is not a virtue when it omits critical information. It is not an appropriately sized description for a tool with nine parameters.

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 tool is complex (9 parameters, no output schema, no annotations), yet the description is a bare noun phrase. It does not explain what the tool does, how inputs relate to outputs, what the expected response format is, or any constraints. The description is wholly inadequate for an agent to call this tool correctly.

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 coverage is 100%, so the parameter descriptions exist, but the tool description adds no semantic linkage between the parameters and the stated purpose. The parameter descriptions (e.g., 'discarded after the shape check') suggest the tool performs validation, yet the description says it's a status-code catalog, creating a mismatch. The description fails to clarify how these parameters map to the tool's function.

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 'Short catalog of common HTTP status codes' is a noun phrase, not a clear verb+resource. It doesn't state what the tool does with its nine input parameters, which are described as shape checks or discarded values in the schema. The name suggests a status-code reference, but the parameters imply a different purpose, making the intent vague and confusing.

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 when-to-use guidance is provided. The description gives no indication of when to select this tool over any sibling (e.g., fetch-status, browser-url-ok). There are no alternatives, exclusions, or context cues, leaving the agent without any selection criteria.

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