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

Annotations cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description isn't obligated to restate them. It adds that there is 'saved evidence' returned alongside status, which is a real behavioral hint. But it omits whether the job must exist, whether reads are idempotent, or whether a completed job retains evidence indefinitely.

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 sentence, front-loaded verb-resource, no filler. Slightly terse given a 1-param schema with no other context, but every word earns its place.

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 needn't be explained, and annotations handle safety. What's missing is the lifecycle context for a durable job: when to poll, what statuses exist, how this pairs with resume_asset_research_job. For a 1-param read tool it's adequate, but the async-job semantics are left implicit.

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 coverage is 0% and there is one required parameter, taskId, which is a UUID. The description says 'one of your durable research jobs' but never explains that taskId identifies the job, its format, or where it comes from. Baseline for a single undocumented param is mid-range; the description neither compensates nor misleads.

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?

States a specific verb (Read) and resource (research job status and saved evidence), and the qualifier 'one of your durable research jobs' hints at the async-job family. It doesn't explicitly differentiate from resume_asset_research_job or start_asset_research, but the noun phrase 'status and saved evidence' is distinct enough from those siblings.

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 when-to-use guidance. The description doesn't tell the agent whether to call this after start_asset_research completes, whether it polls, or how it relates to resume_asset_research_job. The reader must infer the workflow from sibling names alone.

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