find_family

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

No annotations, so description bears the burden. It discloses a key behavioral rule (at least one parameter required) but does not state that the operation is read-only or describe return behavior. The word 'search' implies a read operation, but this is not explicit.

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?

Two concise sentences, front-loaded with the primary action and followed by a critical usage constraint. Every word 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?

The description is adequate for a search tool with an output schema. It covers the main search criteria and the precondition. It does not mention edge cases like empty results or matching semantics, but these are not essential given the output schema depth.

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 description coverage is 0%, so the description compensates by naming and explaining the three main parameters (husband_query, wife_query, marriage_year) and the constraint that one must be set. It does not explain 'limit', but that parameter's purpose is obvious from its name and schema default.

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 searches families by spouse name and/or marriage year, using a specific verb ('search') and resource ('families'). It distinguishes from sibling tools like find_individual and get_family by focusing on family-level search with spouse criteria.

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?

Provides explicit usage context: 'Search families by spouse name and/or marriage year' and a clear constraint that at least one of the three key parameters must be set. Does not mention alternatives explicitly, but the constraint gives clear guidance on valid invocation.

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