fetchForgeReleases

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

With no annotations provided, the description carries the transparency burden. It discloses that hash:true is slow and required before announce, adding behavioral context beyond the schema. However, it does not mention potential failures, rate limits, or whether the operation is read-only, so it is not fully transparent.

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?

The description is two succinct sentences. The first sentence states the core purpose, and the second provides a key usage caveat. No filler or redundant information, earning a maximum score.

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?

Given the tool's simplicity (2 params, no output schema) and lack of annotations, the description covers the main purpose and a critical usage requirement. However, it does not explain the return structure or how it fits with siblings like announceSoftwareFromForgeRelease beyond the 'required before announce' hint, leaving some gaps.

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 baseline is 3. The description adds extra nuance by explaining the hash parameter's role ('slow; required before announce') and clarifies sourceUrl supports GitHub/Codeberg/GitLab forges, which provides value beyond the schema.

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 clearly states a specific action ('Fetch latest public forge Release') and resource (external forges: GitHub/Codeberg/GitLab) along with APK assets. This distinguishes it from sibling tools like listReleases by focusing on external forge releases and asset fetching.

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?

The description provides clear context on when to use the hash parameter: 'required before announce'. It implies this tool is a prerequisite for announcing releases, but it does not explicitly name alternative tools or state when not to use it. This warrants a 4 rather than 5.

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