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

No annotations are provided, so the description carries the full burden. The 'help' framing implies a read-only, side-effect-free lookup, and 'Free.' communicates a payment-related behavior, which is modestly useful. However, it discloses nothing about return format, scope, or limits.

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?

A single front-loaded sentence with no padding; the information type leads. The trailing fragment 'Free.' is slightly awkward and could be folded into the sentence, costing it a perfect 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?

For a zero-param tool the description is nearly enough, but with no output schema and no annotations it should say more about what is actually returned (e.g., pricing details, plan comparison). The 'Free.' note hints at pricing content but the return surface remains undefined.

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?

The tool has zero parameters, so the baseline is 4. Nothing in the description misleads about inputs, and there is no argument surface that needs explaining.

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 states the informational content served (offerings, prices, payment mechanics) and, combined with the name forge_help, an agent can recognize this as the documentation/pricing tool. It is clearly distinct from the render/optimizer/leaderboard/level-design siblings. The only weakness is the absent verb and the fragmentary phrasing.

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, no prerequisites, and no alternatives named. Usage is only weakly inferable from the word 'help'. An agent gets no guidance on what question this tool answers versus simply not calling it.

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