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

The readOnlyHint annotation already covers the safety profile. The description adds one useful behavioral/data fact — the separation of synthetic/researcher-directed results from organic outcomes — but discloses no further behavior such as response shape, pagination, or scoping.

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 very short and the second sentence carries meaningful content. The first sentence nearly restates the tool name, which is mildly redundant, but overall there is no padding.

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?

This is a low-complexity read tool with readOnlyHint and one parameter, so the missing output schema is less critical. Still, the meaning of id is left ambiguous and the description does not state what the returned dashboard content contains beyond the synthetic/organic distinction.

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% and the description does not explain what the required id refers to (dashboard ID, run ID, subject ID). With a single undocumented parameter, the description should at least clarify what id identifies; it does not.

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 names a specific verb and resource ('Read your research dashboard') and adds the dashboard's key semantic: synthetic/researcher-directed results are separated from organic outcomes. It is clear, though it does not explicitly differentiate from sibling tools like read_research_export or read_research_presentation.

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 context is clear: this tool reads a research dashboard and the separated result categories are called out. However, no explicit guidance is given for when to choose this versus adjacent read_research_* tools, and no exclusions or alternatives are named.

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