Get record

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Fetch' clearly indicates a read operation, and it mentions expand/select capabilities, but it does not disclose error behavior, return format, auth requirements, or what happens when the id is not found. Adequate but not rich.

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?

A single, well-structured sentence that front-loads the core operation ('Fetch a single record by id') and places optional capabilities at the end. There is no filler or redundant phrasing.

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?

For a simple read tool, the description captures the essential semantics and the schema fully documents parameters. However, with no annotations and no output schema, some additional detail about return behavior or failure cases would make it more complete. Still, an agent can correctly select and invoke the tool.

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% and all four parameters already have meaningful descriptions. The description's mention of expanding relations and selecting fields mirrors the expand and fields parameters without adding new detail, so it meets the baseline but does not exceed it.

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 uses a specific verb ('Fetch'), a clear resource ('a single record'), and identifies the key differentiators: by id, with optional relation expansion and field selection. This makes it easy to distinguish from sibling tools like list_records, get_full_record_list, and get_first_record.

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 implies this tool is for when you know a record's id and want a single record, but it does not explicitly state when to use it over alternatives like get_first_record or list_records. No exclusion criteria or alternative routing is provided, so usage guidance is only implied.

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