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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the tool returns 'full results,' giving some sense of response richness, but it does not describe error behavior, missing-ID handling, or response structure. With annotations carrying the read-only burden, this is adequate but not rich.

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?

One focused sentence with no redundancy or filler. The verb, object, and distinguishing detail ('by ID') are front-loaded, and nothing is repeated from the title or annotations.

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 simple one-parameter read-only fetch, the description provides enough to select and invoke the tool correctly. The main gap is that 'full results' is vague and there is no output schema, so an agent cannot anticipate the exact return shape; however, the low complexity makes this a minor omission.

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 describes the id parameter as 'The research ID' with a strict UUID format, and schema description coverage is 100%. The tool description adds no extra parameter-level meaning, so the baseline of 3 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 clearly states a specific verb ('Get'), resource ('research'), and selection criterion ('by ID'), and mentions 'full results' so an agent can distinguish this from list_researches and other entity-specific getters. It is immediately actionable.

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 'by ID' phrasing implies this tool is for targeted retrieval once an ID is already known, which is a clear contextual signal. However, it does not explicitly mention when not to use it or direct the agent to sibling tools such as list_researches for finding IDs or get_deep_dive for other entity types.

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