check_module_compatibility

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

No annotations are provided, so the description must disclose behavioral traits, but it only states the check operation without mentioning side effects, error handling, or what 'compatible' means. The agent is left without important context such as whether the tool returns a boolean or raises exceptions.

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 concise, with a one-sentence purpose and a compact Args list. It is front-loaded and contains no verbose filler. However, it could be slightly more informative while still remaining concise, so it does not earn a perfect 5.

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?

The tool is simple (one parameter) but lacks annotations and an output schema explanation. The description does not cover what compatibility means, what happens if the module is absent, or any environmental factors. Given the rich sibling context, more detail is needed for safe and correct invocation.

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 has no parameter descriptions (coverage 0%), so the description must compensate. However, the Args section merely restates the parameter name with 'The module name to check', which is tautological and adds no meaningful detail beyond the property name. It does not explain what constitutes a valid module name or how compatibility is determined.

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 the tool checks if a module is installed and compatible, which is a specific action on a specific resource. It distinguishes itself from sibling tools like list_modules and get_module_info, which serve different purposes (listing and retrieving info, respectively).

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The agent must infer usage from the tool name and context, but no explicit direction is given.

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