get_family

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

With no annotations available, the description carries the full burden of behavioral disclosure. It specifies that the record's husband/wife/children are resolved to summary dicts and that id accepts both '@F1@' and 'F1' formats, adding meaningful context beyond the schema. It does not cover error handling or edge cases, but this is acceptable for a read-only retrieval tool.

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 a single sentence, front-loaded with the primary action and key details. It contains no filler or redundant information, making it concise and well-structured.

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 simple get-by-id tool, the description covers the essential functionality, including the id format and the resolution of relations. Since an output schema exists, the return values are already documented. It lacks explicit alternative-tool guidance and edge-case behavior, but given the tool's simplicity, the description is reasonably complete.

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 provides only the parameter name and type with 0% description coverage. The description compensates by explaining that 'id' identifies a FAM record and gives examples of acceptable formats ('@F1@' or 'F1'), which adds value beyond the bare schema definition.

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 returns a full FAM record for a given id, with husband/wife/children resolved to summary dicts. This precise verb+resource combination distinguishes it from siblings like get_individual or find_family, which target different record types or search behavior.

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?

No explicit guidance is provided about when to use this tool versus alternatives. The name and description imply usage for fetching a family record by id, but there is no mention of exclusions or comparisons to sibling tools like find_family or get_individual, making the usage context only implicit.

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