read_manifest

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value by disclosing the return content (summary, licence, per-file descriptions, file list) and the intended workflow role as a cheap discovery call preceding targeted fetches. It stays silent on what happens with an unknown or unauthorized repoId, which keeps it off 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?

Two sentences, zero filler, and the payload description is front-loaded ahead of the workflow instruction. Nothing could be removed without losing information.

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 one-parameter read-only tool with no output schema, the description is nearly sufficient: it tells the agent what comes back and why to call it first. The only material omission is failure behavior for a bad repoId, which is a minor gap given the simplicity of the operation.

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 0%, so the description must carry parameter meaning and it only implies the target via 'a repo's manifest'. The single repoId parameter is self-explanatory and the schema supplies its uuid format, so the practical risk is low, but explicit format or scoping hints would have been cheap to add.

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?

Uses a specific verb ('Read') against a specific resource ('a repo's manifest') and enumerates the payload the agent gets back: summary, licence, per-file purpose, and the fetchable file list. That is far more than a restatement of the name. It loses the top mark only because the sibling catalog here contains no comparable read tool to explicitly differentiate against.

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?

'Read it before fetching, then fetch only what you need' gives an explicit ordering constraint and an implicit alternative (a separate fetch step). The gap is that the fetch tool is never named, so the agent must infer which sibling to call next from phrasing rather than a direct pointer.

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