Get a single record

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It says 'Fetch full details,' which implies a read operation, but doesn't explicitly state read-only behavior, discuss permissions, or mention the impact of the 'include' parameter on response content. This is a significant gap for a tool with no annotation support.

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, clear, front-loaded sentence with no unnecessary words. It efficiently conveys the primary purpose without fluff.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is too thin. It doesn't explain the 'include' parameter, omits supported modules, and doesn't outline what 'full details' entails. Even for a simple get-by-id tool, this is insufficient for an agent to use it correctly across all valid inputs.

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 already provides descriptions for 'id' and 'include', and the description merely says 'by its id,' adding little new meaning. It partially lists module values but omits two enum options, making the parameter information less complete than the schema. The 'include' parameter is not explained in the description at all.

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 fetches full details of a single record by id, using the specific verb 'Fetch' and naming the resource types. However, it omits 'tasks' and 'appointments' from the schema enum, making the module list incomplete and therefore slightly imprecise.

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 use when you have a record id and need full details, but it doesn't explicitly contrast with sibling tools like search or list_records. No explicit 'when to use' or 'when not to use' guidance is provided.

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