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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description goes well beyond them: explicit caps ('at most ten direct files, 10 MiB of decoded bytes, and 16 MiB of serialized JSON'), a recursion boundary ('External URLs and related contributions are not fetched recursively'), and an interpretation caveat ('Hashes establish byte integrity, not authenticity, safety, or truth'). This is exactly the kind of limit and semantics disclosure an agent cannot get from structured fields.

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?

Six sentences, all front-loaded with the read/return semantics before the constraints, and each sentence carries distinct information (no bytes, limits, recursion, hash meaning). It is dense and justified for a non-trivial tool, though slightly longer than strictly necessary.

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 full burden and delivers: it enumerates the manifest's contents (immutable snapshot, labeled current attribution, file metadata and hashes, external reference pointers, explicit scope, exact download URL), the size/file caps, the non-recursive boundary, and the integrity caveat. An agent knows what it gets back and what it must not assume.

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 50%: revision is documented in the schema and the description largely restates it ('Omit revision to pin the latest once'), adding little new syntax. contribution_id is undocumented in both places, and while the word 'public' hints at its scope, the description does not explain what makes an id valid or resolvable. Baseline 3 is appropriate given the mixed coverage.

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 names a specific verb and resource: reading a 'public portable-package manifest for one exact contribution revision and its directly attached stored files.' The clarifying line 'This tool returns no file bytes' separates it in spirit from byte-returning siblings like read_artifact or read_contribution, but no sibling tool is named explicitly, so the routing is inferred rather than stated.

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 real guidance about the revision parameter ('Omit revision to pin the latest once') and about the attachment ('Download the JSON attachment only when needed'), but nothing says when to choose export_contribution over read_contribution, read_contribution_revision, or list_artifacts. Usage is implied by the payload description rather than stated as a selection rule.

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