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 covered structurally. The description's contribution is the clarifying clause 'No research is started', which usefully confirms this is a passive read, but it adds nothing about auth requirements, staleness, or pagination.

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 no filler. The odd phrasing 'list research status' is the only friction; otherwise it is efficiently sized.

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 not be explained, and annotations cover the safety profile. What remains thin is guidance on the lone undocumented input and when this status read is the right call, leaving it only minimally complete.

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?

There is a single parameter with 0% schema description coverage, so the description must compensate, and it barely does. The only hint is 'accessible sheet', which loosely implies the sheetId must be one the caller can access, but no format, ID source, or failure behavior is given.

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 verb 'Read' plus the resource 'list research status and target' is stated, and it scopes the result to an 'accessible sheet', so an agent can roughly tell what it does. However, 'list research status' is opaque domain jargon and the description never distinguishes this from the other sheets_* siblings (e.g., sheets_get_enrichment_status) beyond the word 'research'.

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?

There is no explicit statement of when to call this versus any sibling, nor any prerequisite beyond the implicit need for an accessible sheet. 'No research is started' clarifies a side effect rather than orienting the agent to a use case, so usage must be inferred.

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