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

Read-only operation (annotations confirm readOnlyHint). Description adds that it returns forges and mentions GraphQL query, providing useful context beyond annotations.

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?

Single concise sentence (22 words) that front-loads purpose and includes relevant details. No wasted text.

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 low complexity and complete schema coverage, description is sufficient. Explains return structure (forges) but omits error conditions or edge cases, which is acceptable for a simple read 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?

Single parameter 'eid' is fully described in schema (100% coverage). Tool description does not add additional semantics beyond 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?

Clearly states 'Fetch a weld' with specific resource 'Anvil workflow' and includes what is returned (forges with fields). Distinguishes from sibling tools like anvil_get_weld_data by specifying inclusion of forges.

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?

Implied usage: when you need a weld by eid. No explicit guidance on when to use over anvil_get_weld_data or other siblings, nor when not to use.

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