Get Account Reports

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

The annotations indicate read-only and open-world hints, and the description does not contradict them. However, it does not add any additional behavioral context such as side effects, error handling, or any constraints beyond listing report types.

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 a single, clear sentence with no unnecessary words, making it highly concise and easy to understand.

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 covers the core functionality but lacks details about the output format or any specific behavior. Given the simplicity of the tool and absence of output schema, it is adequate but not rich.

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 input schema already describes the account_id parameter with a description, so the tool description adds no extra meaning. The description only mentions 'a Canvas account' which is consistent but not additional.

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 that the tool lists available report types for a Canvas account, which is specific and distinguishable from other tools like list_accounts or get_account.

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 provides no guidance on when to use this tool versus alternatives, lacking any context about use cases, prerequisites, or conditions. It only states the action without explaining when it is appropriate.

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