get_family

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

No annotations provided, so description carries full burden. It discloses the returned fields (guardians, children, contacts, balance) but does not mention permissions, error handling, or rate limits. For a simple fetch, it is adequate but could be more thorough.

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 plus an example. The first sentence states purpose, the second provides usage context, and the example illustrates the parameter and return structure. No unnecessary 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?

Given the existence of an output schema (which covers return values), the description adds context by listing key fields and providing an example. It lacks info on error conditions or optional fields, but overall it is sufficient for a simple fetch 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?

With 0% schema description coverage, the description must add meaning. It mentions 'family_id' in the example but does not describe its format or constraints. The single parameter is simple, but lacking details on validation or type.

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 'Fetch a single family by id' and lists the included fields (guardians, children, contacts, balance). While it doesn't explicitly distinguish from sibling tools like get_child or list_families, the different resource names make the distinction clear.

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?

Description provides specific query examples ('what's the balance on family 555?') and shows a typical use case. It doesn't explicitly state when not to use or mention alternatives, but the guidance is sufficient for common scenarios.

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