Canvas API Request

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

Beyond the annotations (which already indicate destructive and non-read-only behavior), the description adds substantial context: irreversible changes for non-GET methods, permission model determined by Canvas account role, and the security implication that returned data is untrusted. This is rich, non-redundant disclosure that exceeds the annotation baseline.

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 reasonably concise and front-loaded with the core purpose, followed by essential safety warnings. Each sentence earns its place, though some phrasing (e.g., 'What this is permitted to do is decided by Canvas...') is slightly verbose. It is not bloated but could be tightened.

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 and dangerous nature, the description covers purpose, endpoint discovery, safety mechanisms (dry_run), irreversible side effects, permission model, and response handling. The presence of an output schema reduces the need to describe return values, and the provided guidance is sufficient for an agent to use the tool safely in context.

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 covers all five parameters with descriptions, so the baseline is 3. The description adds marginal value by mentioning dry_run for previewing and noting that body is for write methods, but these are largely inferable from the schema. No significant additional semantic information is provided beyond the 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?

The description clearly states the tool 'Executes any Canvas API endpoint directly' in the first sentence, establishing it as a direct, general-purpose API access tool. It distinguishes from siblings by emphasizing raw, uncurated behavior and explicitly references 'search_canvas_api' for discovery.

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 gives explicit guidance to find endpoints with search_canvas_api first, and warns about the destructive nature of non-GET methods. It also suggests using dry_run to preview requests. While it doesn't exhaustively enumerate when to prefer curated tools over this one, it implicitly contrasts with 'curated tools' and provides a clear alternative for endpoint discovery.

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