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

Discloses behavior: 'Read-only, no authentication required (public endpoint, IP rate-limited)'. Describes return structure in detail. No annotations present, so description fully covers transparency.

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?

Front-loaded with purpose and usage, then return fields. Slightly long due to detailed return description, but every sentence adds value. No redundancy.

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 no output schema and no annotations, the description is highly complete: explains purpose, when to use, parameter, and return structure. No gaps for the tool's complexity.

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 coverage is 100% with description of slug. Description adds value by clarifying 'listing-level slug, not a contributor slug', which prevents confusion. Baseline 3 plus extra clarification.

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 specifies the verb 'Get', resource 'full detail on one published listing', and identifier 'listing slug'. It clearly distinguishes from siblings like search and list_categories by stating the scope.

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?

Explicitly states when to use: 'Use after search or list_categories to drill into a specific result.' Also notes read-only and no authentication. Lacks explicit when-not but covers key usage context.

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