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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value by enumerating the returned payload (manifest, digest, tree hash, revision, license, links), which is useful given there is no output schema, but it says nothing about auth needs, error behavior, or the single-forge lookup mechanics.

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 an informative field enumeration and no filler. The list is long but each item is meaningful; nothing reads as padding.

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 read-only single-get tool whose annotations cover safety and whose single parameter is fully schema-documented, the description is adequate and usefully enumerates returns in the absence of an output schema. Its main shortfall is not clarifying its relationship to show_forge, leaving a genuine ambiguity for tool selection.

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% and the forgeId field is fully documented in the schema ("id or its slug, exactly as list_forges or get_forge returned it"). The description adds no parameter-level detail beyond this, so the baseline 3 applies.

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?

States a specific verb ("Read") and resource ("one forge") and enumerates the returned content, which lets an agent understand scope. However, it never distinguishes itself from its sibling show_forge, which appears to overlap, so the boundary is left to inference.

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 one forge in full" implies fetching a single forge by id, but there is no explicit when-to-use guidance, no exclusions, and no reference to alternatives such as list_forges or show_forge. With a near-duplicate sibling present, this absence is a real gap.

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