move_modules

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

Annotations declare readOnlyHint=true, and the description confirms a read operation. The description adds context about chain specificity (Available on Initia L1 and Minimove chains) but lacks details on behavioral traits like pagination, limits, or side effects. Annotations already cover the safety profile, so the description adds moderate value.

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 consists of two sentences. The first sentence directly states the main purpose, and the second provides crucial usage guidance and scope. Every word is purposeful, with no redundant or extraneous information.

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 does not explain the return format. For a list tool, knowing the response structure (e.g., module names) would be helpful, but the purpose and usage are adequately covered. The missing output description slightly reduces completeness.

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 100%, with each parameter having a clear description in the schema. The tool's description adds no new details beyond the schema fields; it merely reiterates the chain info. Baseline 3 is appropriate since the schema already defines parameters well.

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 starts with a clear verb+resource: 'List all Move modules deployed at an address.' It also distinguishes itself from the sibling tool 'move_module_abi' by stating 'before calling move_module_abi', making its purpose unambiguous.

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 explicitly states when to use this tool: 'Use this to discover available modules before calling move_module_abi.' It also mentions chain availability, but does not provide explicit when-not-to-use or alternative tools, though the guidance is clear.

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