workflow_get_task_context

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds only that the state is 'persisted' (i.e. durable, not in-memory), with no mention of failure modes, auth needs, or what 'task state' comprises. Some added context, but thin.

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?

A single front-loaded sentence with no filler. It is efficient, though it is arguably clipped to the point of under-specification rather than tightness.

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?

Low-complexity, read-only tool with one parameter and no output schema, so the description should at least sketch what state is returned. It names the resource but not its contents or the identifier's origin, leaving the agent only partly equipped to call it.

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?

The sole parameter taskId has 0% schema description coverage, and the description says nothing about it — no format, source, or how to obtain it. With the schema carrying no meaning and the description not compensating, the agent must guess where the identifier comes from.

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+resource ('Read the persisted task state'), which tells the agent exactly what the tool retrieves. It does not, however, differentiate itself from look-alike siblings such as workflow_get_task_audit or workflow_get_freshness, so an agent must infer the distinction from context.

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?

Gives a timing cue ('before starting or resuming local Copilot work') that implies the usage window, but names no alternatives and no when-not conditions. The agent gets a rough sense of when this fits but no routing logic against the many sibling get_* tools.

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