forge

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

With no annotations, the description carries full burden. It discloses the returned data types and adds a warning about the small rewards and fulfillment counts, giving useful behavioral context beyond a simple 'returns data' statement. It does not mention side effects or authentication, but as a read-only info tool this is acceptable.

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?

Three concise sentences: definition, returns, and caution. It is front-loaded with the core purpose and contains no redundant information. Every sentence adds value.

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 no-parameter, no-output-schema tool, the description covers the key return categories and provides a practical caveat. It could specify the exact structure of the leaderboard or stats, but it gives enough for an agent to decide to call it and interpret the result.

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 and 100% schema coverage (empty schema). Per guidelines, baseline is 4. The description adds no parameter info, but none is needed since there are no inputs.

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 that the Forge is a bounty board and specifies what it returns (open bounties, agents, demand, leaderboard). It distinguishes itself from siblings by being the only bounty-related tool, so an agent can recognize its purpose and resource without confusion.

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?

It implies usage by stating the tool returns bounty-related data, and includes a caution to check stats before relying on income. However, it does not explicitly state when to prefer this tool over alternatives or when not to use it, though the unique purpose makes it largely self-evident.

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