canvas_confirmation_capabilities

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

Annotations already set readOnlyHint, destructiveHint=false, and openWorldHint, but the description adds meaningful behavior: no prompt or Canvas contact, no connector form or elicitation, and unchanged platform approvals. This clarifies the tool's safety and authorization side effects beyond the structured annotations, and it does not contradict the read-only and non-destructive annotations.

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 short and front-loaded, with each sentence adding either scope or a behavioral constraint. The wording is dense but not wasteful, though the line breaks and abstract phrase 'conversational authorization policy' slightly reduce immediate clarity.

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?

For a zero-parameter reporting tool with an output schema and read-only annotations, the description covers purpose, non-contact behavior, and authorization constraints well enough to invoke correctly. It could be stronger with explicit guidance on when to use it versus sibling capability tools.

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 has zero parameters and is fully self-contained, so the baseline is 4. The description adds no parameter meaning, but none is needed for an empty 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 states a specific verb and resource: 'Report conversational authorization policy,' and adds a scope boundary: 'without prompting or contacting Canvas.' It does not explicitly differentiate this from sibling capability tools such as canvas_capabilities, so it falls short of a 5.

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?

No explicit when-to-use or when-not-to-use guidance is provided, and no sibling alternative is named. The statement that user authorization is still required describes a constraint rather than a rule for selecting this tool, leaving the agent to infer when to call it.

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