get_bulk_operation_info

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

The readOnlyHint=true annotation already establishes this is a non-mutating read, so the description's addition of 'status and progress' is useful but modest. It does not disclose whether the result is eventually consistent, how long operation records are retained, or what a completed versus failed operation looks like — all relevant for a job-status endpoint.

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, zero waste, and the resource and lookup key are front-loaded. Nothing redundant and nothing padded.

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 tool with annotations covering the safety profile, this is nearly complete. The one remaining gap is that no output schema exists, so the description could briefly sketch the shape of the returned status/progress rather than leaving the agent to discover 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?

Schema description coverage is 100%, so the single parameter is fully documented in the schema itself. The description's 'by its id' adds no syntax, format, or sourcing detail beyond what the schema's 'Bulk operation id returned by bulk_* tools' already provides, so baseline 3 applies.

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 ('Get'), a specific resource ('status and progress of a bulk change operation'), and the lookup key ('by its id'). An agent can distinguish this polling/inspection tool from the mutation siblings bulk_update_issues, bulk_move_issues, and bulk_transition_issues without opening any schema.

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?

Usage is implied: the parameter note ('Bulk operation id returned by bulk_* tools') tells the agent this is called after kicking off a bulk job. However, there is no explicit when/when-not guidance, no mention that it should be polled until completion, and no named alternative for checking results after the operation finishes.

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