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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new context beyond the annotations: a per-call cost of 0.01 USDC on Base x402 and the need for an X-Provider-Key header when using customer-owned credentials, which matters for both billing and authentication decisions.

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?

Two sentences, front-loaded with what the tool returns followed by cost and auth constraints; there is no filler. The payment sentence is slightly dense ('0.01 USDC on Base x402') but still earns its place.

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 compensates by naming the returned fields (state, branch, timestamps, run URLs), and it covers auth and cost. Missing pieces such as error behavior or rate limits are minor for a simple three-parameter read tool.

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 owner, repo and limit are already documented, and the description adds no format, default-ordering or validation detail beyond what the schema states. The phrase 'latest runs' loosely corroborates the limit semantics but adds little new meaning.

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 description uses a specific verb ('Read') with a well-defined resource: workflow execution state, branch, timestamps and run URLs from a GitHub repository. It is clearly distinguishable from the only close sibling, api_github_pr_review, though it never explicitly names that alternative.

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 mention of alternatives or prerequisites beyond a passing reference to credentials. An agent must infer from the verb that this is for inspecting CI/workflow run status.

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