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

Annotations already provide readOnlyHint=true, and the description is consistent with that. It adds value beyond the annotation by disclosing that the read respects 'current privacy filters' and includes 'reproducible analysis metadata', which are behavioral traits not present in the structured data.

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, front-loaded sentence with no filler. Every word adds meaning, and the key verb and object appear first.

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 read tool with one parameter and a readOnly annotation, the description is adequate, but it leaves gaps: there is no output schema, no clarification of what the returned export contains, and no guidance on when to choose this over closely related research tools. It is minimally viable but not fully self-sufficient.

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% for the single 'id' parameter, and the description does not explicitly explain how id maps to the research export or where to obtain it. The phrase 'owned research export' implies the id refers to an export, but this is indirect and does not compensate for the lack of schema-level parameter documentation.

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 states a specific verb ('Read') and resource ('owned research export'), and adds useful qualifiers about privacy filters and metadata that clarify the object's nature. It is clear, but it does not explicitly distinguish itself from sibling tools like prepare_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?

No guidance is given about when to use this tool versus alternatives. The 'owned' qualifier implies a constraint, but there is no mention of prerequisites, exclusions, or how this differs from related research export/read tools.

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