steamdt_get_inspect_by_url

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

No annotations provided, so description carries full burden. It discloses the rate limit (100/day) and that it's a scarce resource, but does not specify if the operation is read-only or if there are side effects beyond rate limiting.

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?

Two sentences with no wasted words. The first sentence conveys the action and prerequisite, the second adds a critical constraint. Perfectly concise.

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?

No output schema, so description should clarify return format. It mentions '2D inspection view' but does not specify whether output is an image URL, image data, etc. Prerequisite is noted but does not link to the specific sibling tool. Adequate but could be more complete.

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 has 100% description coverage for both parameters. Description adds no additional meaning beyond what is in the schema, meeting the baseline score.

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?

Description clearly states the tool generates a 2D inspection view from a CS2 inspect link. It implies a prerequisite (obtain wear data), which differentiates it from siblings like steamdt_get_inspect_by_asmd, but does not explicitly name alternatives.

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?

Provides a prerequisite (need wear data first) and mentions the rate limit, giving basic guidance. However, it does not explicitly state when to use this tool versus alternatives like steamdt_get_wear_by_inspect_url or steamdt_get_inspect_by_asmd.

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