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

The description reveals no behavioral details such as side effects, return values, or error conditions. With no annotations, the agent has no idea what invoking this tool will do.

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?

The description is very short, which is concise, but it is far too terse to be useful. It lacks any structural breakdown of what the tool does or how the parameters relate to the tool's purpose.

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?

There is no contextual information about the tool's role, expected inputs, or output. The description and schema together do not form a complete picture, leaving the agent unable to make an informed invocation decision.

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 schema parameters have descriptions, but they are generic and unrelated to language tags (e.g., 'Git ref name; discarded after the shape check'). The tool description adds no meaning to these parameters, and their purpose is completely unclear.

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 'ISO 639 language tag ga' is extremely vague and does not explain what the tool actually does. It fails to indicate whether it validates, converts, or checks language tags, and the sibling tool list offers no clarification.

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 guidance on when or how to use this tool. No examples, prerequisites, or conditions are provided, leaving the agent without any practical direction.

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