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

Annotations already cover the read-only safety profile, so the description is free to spend its words on behavior: it explains which fields appear conditionally (queueReason, queue, coalescedFires/coalescedNote, retryOf/retriedAs) and why. That gives the agent real insight into how run state maps to returned data, though it omits any mention of auth or rate limits.

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?

The core purpose is front-loaded in the first sentence, but the bulk is a dense enumeration of conditional output fields that reads closer to an output schema than to guidance. It is not padded with filler, yet the balance is skewed toward field listing.

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?

With no output schema, documenting return fields is genuinely necessary and the description does so thoroughly. However, it leaves owner/repo semantics and any sibling routing unaddressed, so it is complete on returns but incomplete elsewhere.

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 only 33%: run_id is documented ('id, or a unique leading part of it, 8+ hex characters') but owner and repo have no schema description, and the description says nothing about any parameter. With low coverage the description should compensate for owner/repo semantics and 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?

States a clear verb and resource: 'Fetch a workflow run's metadata + status,' and adds that it mirrors GET /api/v2/repos/.../actions/runs/:id, which pins down exactly what is retrieved. It does not explicitly contrast with siblings like merjax_list_workflow_runs or merjax_get_workflow_logs, so it stops short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The description never tells the agent to prefer this over merjax_list_workflow_runs when scanning or over merjax_get_workflow_logs when logs are needed; usage is only inferred from the verb.

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