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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds genuinely new behavioral facts: no network fetch occurs, no signup/auth is required, and the operation is deterministic. That is meaningful context beyond the annotations, though it says nothing about return format or edge-case handling (malformed URLs, non-HTTP schemes).

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?

A single front-loaded sentence stating the action, then three terse qualifiers. No padding, and the most decision-relevant constraint ('without fetching') comes early.

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 2-parameter, no-output-schema utility with annotations present, the description covers the core action and safety-adjacent traits. It still leaves the removeAllQuery parameter's semantics and the return value (cleaned URL string? object?) unstated, which is a real gap for an agent deciding how to call it.

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% for both parameters. The description implies a default of removing only 'common tracking parameters', which hints at what removeAllQuery toggles, but it never explains that boolean or the url parameter's accepted format. With zero schema documentation, the description does not compensate.

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?

States a specific verb and resource: 'Remove common tracking parameters from HTTP links'. The qualifier 'without fetching' implicitly separates it from fetch/extract siblings like penny_html_extract. However, no sibling is named, so the differentiation is inferential rather than explicit.

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 phrase 'without fetching' implies the usage condition (when you have a link and want it normalized offline rather than retrieved). But there is no explicit when-to-use statement, no exclusion, and no named alternative among the many penny_* siblings, so the agent must infer the trigger.

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