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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior, so the description does not need to restate safety. It adds useful context about exact-id-only lookup and an HGRApi Header/channelOAuthId prerequisite, though it does not describe edge-case behavior such as missing ids or partial results.

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 definition is front-loaded with the core behavior, followed by targeted exclusions and alternatives. Every sentence contributes to correct tool selection or invocation, with no filler.

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 rich annotations, full schema coverage, and an output schema, the description covers purpose, exclusions, alternatives, and auth prerequisites well. A minor gap remains around whether at least one of listingIds or primaryIds must be supplied, since only channelOAuthId is required in the schema.

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 the schema already documents listingIds, primaryIds, and channelOAuthId in detail. The description reinforces that identifiers must be concrete and already known, but adds little parameter-level meaning 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?

States a specific verb and resource: gets exact listings by concrete HGR listing ids or visible marketplace primary ids. It clearly separates this from bulk/global listing discovery and explicitly names the active, pending, and terminated listings 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 explicit when-to-use guidance (only when exact ids are already known) and when-not-to-use guidance (discovery, scanning, ranking, filtering, aggregation, and CSV/XML/XLSX/feed exports). It also routes bulk/global queries to named sibling tools.

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