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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral detail beyond that: it downloads the zip, extracts it, and returns the contents of text/JSON files inside (implying binary content is not returned). It omits any size/rate limits on large artifacts, keeping it short of a 5.

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?

Four tight sentences, front-loaded with the core action and then scoping/prerequisite guidance. Minor redundancy with the schema's parameter notes, but no wasted padding.

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 read tool with no output schema, the description usefully explains what is returned (text/JSON file contents from the extracted zip) and how to obtain inputs. With readOnlyHint covering safety, the agent has enough to invoke it correctly; only edge cases like oversized or binary artifacts are left unstated.

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 schema already documents repo, owner, and artifact_id. The description largely restates the schema's 'owner/name' form and owner-preference guidance, adding little beyond what structured fields provide. Baseline 3 is appropriate.

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+resource: 'Download and read the contents of a GitHub Actions artifact'. It clearly distinguishes itself from siblings like github_list_artifacts (which only enumerates) and github_read_file (repo files, not artifacts).

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?

Explicitly names the prerequisite tool ('Get the artifact_id from github_list_artifacts first'), the owner source ('Prefer the exact owner from github_list_repositories'), and concrete use cases (Trivy scan results, test reports, CI/CD outputs). An agent knows exactly when and how to reach for this tool.

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