list_module_items

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

ReadOnlyHint annotation provides read-only attribute, and description 'list' is consistent with non-mutating role. Doesn't go beyond pub annotations: natural amplification info e.g. no mention of permissions, response shape or side effects.

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 line, direct and no redundancy.

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?

Three descriptive parameters, 100% schema note coverage, clear output types. The returned page/resource isn't specified in description, but readOnlyHint plus schema enough. Simple read-only operation with standard params and intention.

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 is 100% detailed, and the description is in agreement with the parameters. The description mentions include_content_details but the default, and this is a level from a schema.

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?

Description uses precise action 'List items within a specific module, including pages'. Includes distinct resource 'module scope' and indicates content breadth. This differentiates from siblings by targeting module items (module_id/course_identifier) and outlines pages.

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 intended use context (when to list module items) is implied but not explicitly explained as a choice against sibling tools such as get_pages or list_course_items. Notes no exclusions/exceptions/alternatives.

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