canvas_create_account_report

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Generate a report' implies a read-only or data-processing operation, but it does not specify if this is a creation/mutation (e.g., generating a new report file) or a retrieval, nor does it detail permissions, side effects, or output format. This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and easy to parse, though it could benefit from more detail to improve clarity and completeness.

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 the tool's complexity (3 parameters, including a nested object for 'parameters'), lack of annotations, and no output schema, the description is insufficient. It does not explain what the report generation entails, what the output might be, or how to use the parameters effectively, leaving users with incomplete context for proper tool invocation.

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 clear descriptions for 'account_id', 'parameters', and 'report'. The description does not add any meaning beyond the schema, such as explaining what 'parameters' might include or what 'report' types are available. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but no extra value is provided.

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 states the tool's purpose as 'Generate a report for an account', which includes a verb ('Generate') and resource ('report for an account'), making it clear what it does at a high level. However, it lacks specificity about what kind of report or what the report entails, and it does not differentiate from siblings like 'canvas_get_account_reports', which might retrieve existing reports rather than generate new ones.

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. It does not mention prerequisites, context, or exclusions, such as when to use 'canvas_get_account_reports' for retrieving reports instead. Without this, users must infer usage from the tool name and schema alone.

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