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

The description discloses the side effect of counting a visit and implies a redirect via '302 hop'. However, it does not explain the full behavioral impact, such as whether a redirect URL is returned, whether the request follows the redirect, or any authorization implications.

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 extremely concise and free of fluff, leading with the core action. However, the jargon '302 hop' and the parenthetical add some ambiguity, preventing a perfect score.

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?

With no output schema and no annotations, the description should explain what the caller receives and what happens after the redirect, but it does not. The lack of response/return information leaves important context missing for an agent deciding whether to call this tool.

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 only parameter 'id' has 100% schema description coverage ('ID of the listing to visit'), so the description adds little beyond the schema. The mention of 'listing's origin' slightly clarifies the id's role but does not materially improve parameter understanding.

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 '302 hop to the listing's origin' indicates an HTTP redirect action but 'origin' is ambiguous and the purpose is only vaguely stated. It does not clearly differentiate from siblings like get_listing or like_listing beyond implying navigation.

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?

There is no guidance on when to use this tool over alternatives such as get_listing or like_listing. No conditions, prerequisites, or exclusions are provided.

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