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

Annotations carry the readOnlyHint=true safety profile, so the description need not restate safety. The 'immutable' trait adds genuine behavioral context — every call returns stable, repeatable content, so results are idempotent and safe to cache — and scoping the result count to eight is useful. No contradiction with the read-only annotation.

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?

A single 12-word sentence, front-loaded with the verb 'Read'. The scoping modifier 'immutable' and content detail 'limits of inference' each carry information — zero filler or repetition.

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 zero-parameter, read-only reference tool, the description conveys what content to expect: eight immutable research definitions plus their inference limits. The only omission is the return format of a definition, which is minor given the low complexity and absence of an output schema.

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 tool accepts zero parameters, so there is nothing for the description to explain beyond the empty schema; baseline 4 applies.

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 has a specific verb ('Read') and an exact resource ('the eight immutable research definitions and their limits of inference'). The specificity — a fixed count of eight, immutability, and inference limits — clearly distinguishes it from sibling research readers (read_research_dashboard, read_research_mappings, read_research_presentation), which consume data artifacts rather than definitional content.

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?

No explicit when-to-use or exclusion criteria is provided, and no alternative tools are named. The intended use is implied — consult this reference when research definition constraints or inference limits are needed — but an agent gets no explicit signal for choosing this over the many research siblings.

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