getRecord

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral fact that this expects a pre-existing ID from a prior lookup, implying it is not a search entry point. It says nothing about failure behavior for unknown IDs, and the output schema covers the return shape.

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?

Two short sentences with zero filler, and the core action is front-loaded before the usage condition. Every sentence earns its place.

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 trivial single-parameter lookup with full schema coverage, an output schema, and safety annotations, the description supplies everything an agent needs: what it fetches, and when the ID precondition holds. Nothing material is missing.

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 one parameter at 100% schema coverage, the schema already documents recordId as 'ID of the record to retrieve.' The description's 'by its ID' simply restates this, adding no format or sourcing detail beyond the schema. Baseline 3 is appropriate when the schema does the work.

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?

States a specific verb and resource: 'Fetch a single record by its ID.' The word 'single' and 'by its ID' distinguish it from search-style siblings like findRecords and findOneRecord. It does not explicitly name getRecordsByIds, the closest sibling for plural ID lookup, so full sibling differentiation is missing.

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?

Gives an explicit precondition: 'Use when you already have the ID from a previous findRecords or findOneRecord call.' It names the two sibling tools that produce the ID, which is actionable routing guidance. It stops short of stating when to prefer this over getRecordsByIds for multiple IDs, but the context is clear.

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