Module Get

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

No annotations are supplied, so the description carries the full burden. 'Get' correctly signals a read-only remote fetch, which is the key safety trait, but nothing is said about network/auth requirements, rate limits, or behavior when the module does not exist. Acceptable but thin for a tool with zero annotation coverage.

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?

One front-loaded sentence with zero filler; the verb, resource, source, and identifier type all appear before any lesser detail. Nothing needs trimming.

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?

An output schema exists, so return values need no explanation, and this is a simple read tool. However, the unresolved project_id vs. machine-name ambiguity and the absence of any failure/edge-case context leave it merely adequate.

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 0%, so the description is the only source of meaning for the single parameter. It adds real value by identifying the expected input as a machine name, but the schema names the field 'project_id', creating potential ambiguity between a Drupal.org numeric project ID and a project machine name.

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?

Specific verb + resource + source: 'Get module details from Drupal.org by machine name' tells the agent exactly what is retrieved and from where. It does not explicitly distinguish itself from nearby siblings like module_search, module_versions, or inventory_modules, but the 'details by machine name' framing is clear enough.

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 phrase 'by machine name' hints at the required identifier, but there is no guidance on when to use this versus module_search (discovery), module_versions (version listing), or inventory_modules (local modules). No prerequisites or exclusions are stated.

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