capabilities

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

With no annotations present, the description must carry the burden of behavioral disclosure. It states the tool reports information, which implies read-only, but it does not explicitly confirm the absence of side effects, nor mention any authentication, latency, or output-size implications of being called first in a session.

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, no filler. The core function is stated first, and the usage instruction is a separate, front-loaded directive. Every word earns its place.

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-parameter tool with no output schema, the description covers what the agent receives and when to call. It stops short of describing the exact shape of the routes/counts/metadata-source data, but that level of detail is rarely needed before invoking a discovery tool.

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 per the rubric. The description adds context about what the returned report covers, which is the relevant semantic information an agent needs.

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 uses a specific verb (Report) with a clear resource (Forge instance) and enumerates the exact content of the report (routes, counts, metadata sources). This distinguishes it from sibling tools like model_profile or generate, which are about particular resources rather than an instance-wide overview.

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?

Explicitly instructs to call this tool first in a session, giving an unambiguous trigger condition. Since no sibling serves an overview/discovery role, there is no alternative to contrast, and the instruction is sufficient.

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