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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds useful return-content detail (exports, signatures, docstrings) but does not mention error behavior, permissions, or completeness guarantees. With annotations carrying safety, a 3 is appropriate.

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 extremely short and front-loaded, with no wasted words. However, it is a fragment rather than a structured sentence and is too compressed for a tool with required parameters, so it sacrifices necessary detail for brevity.

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 and read-only, and annotations plus the mention of returned fields cover some ground. But with two required, undocumented parameters and no output schema, the description does not provide enough for reliable invocation; it should explain module name/version expectations and differentiate from search/list siblings.

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 coverage is 0% and the description never mentions the two required parameters. It does not clarify that 'name' is a module name, what version format 'forVersion' expects, or how the two combine; the agent must infer this from property names alone.

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 identifies the resource and returned content ('Full module: exports + signatures + docstrings'), making clear this retrieves complete reference material for a module. It does not explicitly contrast with sibling stdlib_modules or stdlib_search, so a 4 rather than 5.

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?

No when-to-use guidance or alternatives are given. The agent is not told to use stdlib_search to find a module or stdlib_modules to list modules, nor when this full-reference tool is preferred.

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