get_register_record

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

With no annotations, the description carries the full burden: it discloses the kinds of details returned (parents, occupations, residence, witnesses, volume/page) and implies a read-only lookup. However, it does not explicitly state side effects, permissions, or behavior when the id is invalid or missing.

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 dense sentence with no wasted wording. Purpose, id source, examples, and return categories are front-loaded efficiently.

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?

An output schema exists, so the return values need not be fully documented. The description still usefully names the main data categories and explains how to obtain record_id, though it could be slightly more explicit about the tool's read-only nature.

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 input schema has 0% description coverage and does not explain record_id. The description compensates by saying the id comes from search_records, which gives the parameter clear provenance and usage context.

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 states a specific retrieval action for a specific resource: full details of an indexed register entry by id. It gives examples (birth, marriage, title deed) and explicitly ties the id to search_records, which distinguishes it from the sibling search tool.

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 clearly indicates the tool is used after search_records to retrieve an entry by its id. It does not explicitly exclude alternatives such as get_page or volume_pages, so it stops short of full when/when-not guidance.

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