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

Discloses read-only, no auth, rate limiting, and lists return fields. Lacks details on error handling for invalid slugs, but given it's a public endpoint, this is a minor gap.

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?

Concise 4-sentence paragraph. Front-loaded with main action, followed by return fields and usage context. No wasted words.

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, but description thoroughly lists return fields. Explains slug usage and how to obtain it from siblings. Covers all essential aspects for a single-parameter 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?

Schema has one parameter (slug) with description. Description adds context about slug source ('found in contributor field of search or fetch result') and emphasizes it is not a listing slug. Schema coverage is 100%, so baseline is 3; description adds value.

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?

Clearly states 'Get a contributor's public profile and their published listings' with specific verb and resource. Distinguishes from siblings by specifying 'by contributor slug (not a listing slug)' and referencing use cases for search and fetch.

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 it is read-only, no authentication required, and IP rate-limited. Provides clear when-to-use guidance ('to learn more about who built a listing returned by search or fetch') and what not to use it for ('not for looking up a listing directly').

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