get_record

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

No annotations are provided, so the description must carry the burden. It discloses that the tool returns 'JSON with the complete record or error if not found,' which is useful. However, it does not mention whether the operation is read-only, requires special permissions, or has other side effects. This is a moderate disclosure but not comprehensive.

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 concise and well-structured with a summary line, args, returns, and an example. It is front-loaded with the purpose and each section adds value without unnecessary verbosity.

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 two-parameter read tool, the description is nearly complete. It covers the return type, error behavior, and includes an example. It does not discuss potential edge cases like invalid table names or RID formats, but the output schema likely covers return structure. Overall, it is adequate with minor gaps.

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 fully compensates by explaining both parameters: 'table_name: Name of the table containing the record' and 'rid: The RID of the record to fetch.' It also includes a concrete example that illustrates the expected argument formats.

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: 'Get a single record by its RID.' This is a specific verb (Get) plus resource (single record) and mechanism (by RID). It distinguishes from siblings like get_table_sample_data or preview_table by emphasizing a single record lookup by RID.

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 when to use it: when you have a RID and need the full record. The Args and Returns sections clarify the expected inputs and output. However, it does not explicitly compare with alternatives or state when not to use it, so it stops short of a 5.

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