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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description should add something else; instead it introduces ambiguity about whether the tool itself verifies 'workflow authority' or merely requires the caller to have done so. No mention of error behavior, authorization failures, or job lifecycle states.

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 short sentence with no filler is good, but the brevity comes at the cost of clarity rather than being earned concision. The most important information (what resource, what precondition) is expressed in abstract nouns.

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 safety. But for a parameterized lookup tied to an authorization concept, the description omits what the id is and what the authority check implies — the two things an agent actually needs before calling.

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 with 0% schema description coverage — the schema only supplies a UUID regex, not a name — so the description bears the burden of explaining what the id refers to. It says nothing, leaving the agent to guess whether it is a job id, workflow id, or operation id.

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' is specific, but the resource is described obliquely as an 'initiated operation' rather than a job, leaving the agent to infer that jobs_get returns job status/details. It also fails to distinguish this tool from the nearby operations_resolve sibling, so the agent has no basis for choosing between them.

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?

The clause 'after checking its underlying workflow authority' hints at a precondition but never states who performs that check or what to do when it fails. No when-to-use, when-not-to-use, or alternative tool is named despite many plausible siblings (operations_resolve, campaigns_get, uploads_get).

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