enumerate_modules

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

No annotations provided. The description discloses the read-only nature and return fields, but does not mention permissions, side effects, or limitations (e.g., whether modules are listed for all sessions or only live sessions). With zero annotations, the description only partially covers behavioral transparency.

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 two sentences, front-loaded with the action and return values. Every sentence adds value without unnecessary words.

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 no output schema, the description usefully explains return fields. However, it lacks details about the session parameter and potential errors or empty results. The tool is simple, so completeness is adequate but not thorough.

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 only parameter 'session' is required but not explained in the description (e.g., how to obtain it, accepted formats). Since schema description coverage is 0%, the description should compensate but does not. The agent may not know how to provide a valid session identifier.

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 specifies the verb 'List' and the resource 'modules loaded in the session's target process,' clearly distinguishing it from sibling tools like enumerate_exports. It also lists the return data (base address, size, path), ensuring the agent understands what the tool provides.

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 explicit guidance on when to use this tool vs alternatives (e.g., enumerate_exports). The description implies it's for listing all modules, but does not exclude other use cases or state prerequisites like an active session.

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