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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false. The description reinforces this with an explicit non-mutation statement ("Does not change or fix the GEDCOM file") and details the output structure (individuals sheet, families sheet, Checks sheet with the specific validation rules), which tells the agent what to expect beyond the flags. The only shortfall is that the return details partially duplicate the output schema rather than adding new behavioral context like size limits or processing time.

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 structure is well front-loaded: when-to-use and sample utterances come first, then parameters, then return contents, then exclusions. It is dense and the long enumerated Checks list makes one sentence heavy, but nearly every clause carries actionable information for selecting or calling the tool.

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?

With an output schema present and 100% parameter coverage, the description does not need to explain return values but does anyway, and it closes the loop on scope by ruling out repair, research, and charting. Nothing an agent needs in order to select this tool over generate_pedigree_chart or to supply the right input is missing.

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 100%, so the baseline is 3. The description goes slightly beyond by framing the two inputs as a routing decision at the top level ("Pass the attachment as file or pasted text as gedcom_text"), confirming file is preferred, though it does not add format or size constraints that the nested schema lacks.

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 names a specific verb and resource (convert a GEDCOM file to an Excel workbook) and extends it with concrete use cases (list everyone in the tree, check for errors). It explicitly distinguishes itself from the only sibling by naming generate_pedigree_chart for charting, so an agent can route without opening either schema.

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 gives explicit trigger phrases ("open my gedcom in excel", "find mistakes in my family tree file") plus a clear when-not list: it does not fix the file, research records, or draw a chart. The alternative for the chart case is named outright, which is the strongest form of routing guidance.

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