get_record

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

No annotations are provided, so the description carries the full burden. It only says 'Fetch', implying a read operation, but does not explicitly state that it is read-only, idempotent, or what happens on failure (e.g., record not found). It lacks behavioral details such as performance implications or authorization requirements.

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 of 10 words, which is very concise. It front-loads the core purpose. However, it could be slightly expanded to include usage guidance without becoming verbose, but it is not overly brief.

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?

While there is an output schema (not shown), the description does not reference it or explain the return value. For a tool with two required parameters and no annotations, the description lacks completeness regarding behavior, error handling, and concrete interpretation of parameters.

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?

With 0% schema description coverage, the description adds minimal context: only that the record is fetched 'by id from the given module'. It does not explain what 'module' represents (e.g., table, data source) or the expected format of 'record_id'. This adds little value beyond the parameter names.

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 verb 'Fetch' and the resource 'single record', and identifies the key parameters 'id' and 'module'. It effectively distinguishes from sibling tools like list_records and search_records, as it is for fetching exactly one record by its ID.

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 alternatives like search_records or list_records. It does not mention contexts such as 'when you have a record ID and need the full record' or edge cases like record not found.

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