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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds one useful privacy note ('No identifiers are retained') but fails to state that the operation is read-only, what the output looks like, or whether any side effects occur. For a tool that accepts file paths and URLs, the absence of safety context 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 two sentences and very short, which is concise. However, it's under-specified: the first sentence is vague and the second is a privacy note. It's appropriately front-loaded in that the purpose comes first, but the purpose is too ambiguous to be useful. It's not bloated, but it's also not informative enough for a tool with 9 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?

Given 9 parameters, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what 'classified' means, what the output will be, how the parameters relate to each other, or when to use this catch-all versus a specialized sibling. An agent has almost no basis for correct invocation.

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 all 9 parameters have individual descriptions (e.g., 'discarded after the shape check', 'no disk access'). The description itself adds nothing about parameters, but the baseline is 3 because the schema already documents them thoroughly. The description's generic phrasing doesn't compensate or add value beyond the schema.

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 verb ('Show') and a resource ('request') but leaves 'classified' undefined. It doesn't specify what classification means, what categories exist, or how it differs from the many sibling shape-check tools like domain-shape, jira-key-shape, or validate-json. It's not a tautology, but it's vague enough that an agent cannot infer its unique role.

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 given on when to use this tool versus the 28 siblings. The description doesn't mention alternatives, conditions, or exclusions. An agent has no way to decide whether to call this or a more specific tool like browser-url-ok or fetch-status.

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