read_module_summary

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explains that list dimensions are automatically resolved to their topLevelItem and that one call returns both line item metadata and cell data. This provides meaningful insight beyond the tool's name and purpose.

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 three concise sentences, front-loaded with the primary purpose. Each sentence adds valuable information: what it reads, how it handles list dimensions, and what the return payload includes. No wasted 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?

The description adequately covers the tool's core function, key behavior, and return contents despite lacking an output schema. It does not mention potential errors, prerequisites, or edge cases, but for a read tool with simple parameters, it provides the essential context needed for an agent to use it correctly.

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%, so both parameters (model and module) are already described. The tool description adds limited parameter-specific meaning beyond the schema, offering only general context about module data. This meets the baseline for high schema coverage but does not significantly enhance parameter understanding.

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 clearly states the tool reads a 'pre-computed rollup of a module's data', using a specific verb and resource. It distinguishes itself from the sibling read_module_detail by emphasizing 'rollup' and 'aggregated results', making its purpose distinct.

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 implies this tool is for summary/rollup data rather than detailed data, but it does not explicitly state when to use it versus alternatives like read_module_detail. It mentions 'automatically resolves list dimensions to topLevelItem', which hints at its use case, but lacks direct guidance on choosing between tools.

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