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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one extra fact beyond that -- 'No research is started' -- confirming this is a pure observation call, but it says nothing about permissions, freshness, or what 'target' means.

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?

Two short sentences with the read scope front-loaded and the no-side-effect caveat second. No filler, though 'latest list research status and target' is a slightly tangled noun phrase.

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?

An output schema exists, so return values need no explanation, and annotations cover safety semantics. For a single-parameter read tool the description is nearly complete; only permission requirements and the meaning of 'target' remain unstated.

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?

Only one parameter (sheetId, a UUID) exists, and schema description coverage is 0%, so the description should carry meaning. It only obliquely notes the sheet must be 'accessible', which hints at a permission requirement, but the parameter name is largely self-describing, so this is adequate rather than compensating.

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 ('Read') and resource ('list research status and target') for a sheet, and the clause 'No research is started' implicitly contrasts it with the sibling sheets_research that does start one. The phrasing 'latest list research status and target' is a little awkward, but an agent can identify the operation.

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?

Usage is implied: check the status of an existing research run. The line 'No research is started' steers the agent away from expecting side effects and hints that sheets_research is the tool that starts work, but no alternative is named explicitly and no prerequisites are given.

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