get_family

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

With no annotations, the description must convey behavioral traits. 'Fetch' clearly indicates a read operation, and the description enumerates what the returned record contains, which is valuable. It doesn't mention error handling, rate limits, or authentication, but for a simple fetch tool, this is sufficient 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?

The single-sentence description is information-dense but not bloated. It front-loads the key action ('Fetch') and then lists the specific data returned. The sentence is slightly long but remains readable and every phrase earns its place.

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 there is no output schema and only one parameter, the description adequately explains what the tool returns (lifecycle dates, part numbers, score factors, bulletin URLs). It also clarifies the input source. It doesn't detail output structure or error cases, but for a straightforward fetch tool, the description provides sufficient contextual completeness.

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 provides a clear description of the slug parameter (type, example). The description adds valuable context by explaining where the slug originates (from search_models or lookup_part pageUrl), going beyond the schema and helping the agent obtain a valid 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?

The description clearly states the tool fetches a full source-backed record for one product family by slug, with specific content types (lifecycle dates, part numbers, support runway score factors, vendor bulletin URLs). This distinguishes it from siblings like lookup_part, which presumably focuses on individual parts.

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 explicitly indicates the slug comes from search_models or lookup_part pageUrl, providing a clear source for the input. It implies when to use this tool (when you need family-level data) but does not explicitly contrast with alternatives beyond the source hint. The guidance is clear but not exhaustive.

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