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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds two pieces of context beyond that: "Owner scope enforced" (access is restricted to the caller's own tasks) and "bounded" events (responses are capped in size). It does not state behavior for unknown or not-yet-existent task IDs, but the added context is meaningful.

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, front-loaded sentences with no filler; the action and scope lead. The telegraphic style ("source artifact" singular, "bounded task events") costs a little clarity for its brevity, but nothing is wasted.

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 single-parameter, read-only tool with no output schema, the description covers access scope and the general content of the response. It is still incomplete on the one thing an agent must supply — the taskId and how it is obtained — and does not say what happens when the task is still queued or missing.

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 one required parameter (taskId, a UUID) with zero description coverage in the schema, and the description never mentions it or explains what it identifies or where it comes from. With low schema coverage the description should compensate, and 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?

"Read your queued/finished research, source artifact and bounded task events" names a specific verb (read) and concrete resources (research results, artifacts, events), which separates it from create_research_task and cancel_research_task. The phrasing is compressed and "bounded task events" is left undefined, so it is clear in outline but not fully precise.

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?

"queued/finished" implies this is the polling/retrieval call to use while a task is still running or after it completes, which is useful implied guidance. However, there is no explicit statement of when to use this versus verify_research_receipt or how to obtain a taskId in the first place, so the agent must infer.

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