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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description goes well beyond that by explaining run-relationship semantics (retryOf/retriedAs), queue-reason diagnostics, workClass slot sharing, and schedule coalescing — genuinely useful behavioral context for interpreting results.

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?

Front-loaded with the core purpose in the first sentence, then dense field-level detail. Every sentence carries substantive information, though the long run-on field inventory lacks bullets and the meta phrasing "Also says how it relates to..." is slightly awkward.

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, the description carries the burden of explaining return values and does so thoroughly. Annotations cover safety; the only material gaps are error/not-found behavior and the undocumented owner/repo parameters.

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 (accepts a unique 8+ hex prefix) but owner and repo are bare strings. The description adds no meaning whatsoever for any parameter, so it fails to compensate for the low coverage as the rubric requires.

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 and resource: "Fetch a workflow run's metadata + status," and anchors it to the upstream API route. It is clearly a single-run read, distinguishable by name from gluecron_list_workflow_runs, but the description never explicitly contrasts itself with that sibling or with gluecron_get_workflow_logs.

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 statement, no exclusions, and no named alternatives among the many workflow-related siblings (list_workflow_runs, get_workflow_logs, ci_queue_status). Usage is only implied by the described fields (inspecting retries, queue reasons, coalesced schedule fires), which is the definition of implied guidance.

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