Family System Pattern

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

Annotations already declare readOnlyHint=true, destructiveHint=false. The description adds no behavioral context beyond the group tag. It does not describe what happens during execution (e.g., returns signatures, requires multiple charts).

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 extremely short (one line plus group tag), which is concise but at the cost of informativeness. It is not structured to aid understanding.

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 provides almost no context for a complex tool with a nested array parameter and no output schema. It lacks details on what 'signatures' are, how many members required, or any examples. Completely inadequate.

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 single parameter 'members' is not explained in the description. Though the schema includes a description for the items, the tool description itself adds nothing. With schema description coverage at 0% per context, the description should compensate but fails.

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?

Description uses vague noun phrase 'System-level family astrological signatures' without a verb or clear action. It does not specify what the tool does (e.g., computes, analyzes, lists). Compared to siblings like 'family_genogram' which imply a structure, this is ambiguous.

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 guidance on when to use this tool vs alternatives like family_genogram, family_parent_child_deep, etc. No context for selection criteria.

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