get_family

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

With no annotations provided, the description carries the full burden. It discloses read-only behavior, the unknown-slug response (found:false, never an error), and details what data is returned. It does not cover auth requirements or rate limits, but for a one-parameter read-only lookup, the transparency is strong.

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 two sentences, front-loading the main purpose and then providing behavioral details. Every phrase contributes value, with no redundancy or fluff.

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?

For a single-parameter tool with no output schema, the description fully covers what the tool returns, how to obtain the slug, and error behavior. It leaves no significant gaps for an agent to invoke it correctly.

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 schema already describes the slug parameter with an example, but the description adds crucial context by specifying the slug comes from search_models or lookup_part pageUrl. This gives the agent a clear source for valid slugs, going beyond the schema's basic label.

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 uses a specific verb ('Fetch') and clearly defines the resource ('full source-backed record for one product family by slug') and its contents. It distinguishes itself from siblings by focusing on a single family's comprehensive record, unlike search or part-related tools.

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?

It explains when to use this tool—when you have a slug from search_models or lookup_part pageUrl—and clarifies that an unknown slug returns found:false with a hint. However, it does not explicitly state when to prefer alternatives like bulk_check or list_vendors, so it lacks explicit exclusions.

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