Get one record

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

The readOnlyHint annotation already establishes safety, and the description adds meaningful behavior: optional eager-loading of related records in the same call. It does not explain raw mode or default include behavior, but the core read semantics are transparent and align with annotations.

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, well-structured sentence that front-loads the core purpose and then adds the key optional behavior. There is no redundant or filler language.

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?

With no output schema and no parameter descriptions, the description is too sparse to fully support correct invocation. The agent still has to guess what 'resource' values are valid, what 'raw' does, and what the response shape looks like. The relationship-include guidance is helpful but not enough.

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 must compensate for all four parameters. It explains the purpose of 'id' and loosely hints at 'include', but it never clarifies 'resource' or 'raw', which are both undocumented in the schema and the description. This is a significant gap.

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 ('Read') and clear object ('one record by id'), which distinguishes it from sibling tools like productive_list and productive_create. The added phrase about pulling related records also separates it from naive relationship-stub traversal.

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 conveys when to use the tool: when you need a single record by id and optionally want related records in one call rather than following stubs. It does not explicitly exclude alternatives like productive_list for multiple records, so it stops short of full when-to-use guidance.

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