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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. However, the description adds only a minor scope clarification ('bride or groom') and does not disclose search behavior, pagination via start/number_show, or how matching works, leaving behavioral aspects unclear.

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 with zero wasted words, front-loading the verb 'Finds' and resource 'marriage records'. It is appropriately sized for the minimal content it provides, earning high marks for efficiency.

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 6 parameters, 2 required, no output schema, and no parameter descriptions, this tool needs a richer description to be usable correctly. The current sentence omits essential details about required inputs, optional filters, and return values, making it far from 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?

Schema description coverage is 0%, so the description must compensate. It only loosely hints that name1/name2 may correspond to bride or groom, but does not define these fields explicitly, nor does it explain start, eventyear, eventplace, or number_show. This is inadequate given the absence of schema descriptions.

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's function: 'Finds marriage records of couples (bride or groom)'. It uses a specific verb and resource, distinguishing it from get_births and get_deaths, though it could be more explicit about how it differs from general search tools like search_records.

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?

The description provides no guidance on when to use this tool versus sibling alternatives such as search_records or browse_transcriptions. No exclusions or preferred usage scenarios are mentioned, leaving the agent without decision support.

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