assignment-page-builder

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

With no annotations, the description carries the transparency burden. It explains this is a methodology (the HOW) and that policy lives elsewhere, which adds context beyond the name. However, it does not disclose concrete behavioral effects, side effects, or prerequisites, such as what happens when invoked or what permissions are needed.

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 front-loaded with the core purpose and provides useful distinctions (code vs. method, global vs. per-course, policy references) in a compact form. Each sentence earns its place, though some redundancy could be trimmed.

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 zero parameters and the presence of an output schema, the description adequately covers what the tool is and when to use it. It explains the relationship to the skeleton and per-course skills, but lacks a bit of detail on the expected outcome or workflow steps, though this may be intentionally deferred to the referenced skills.

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 tool has zero parameters, so the schema is trivially complete. The description adds context by explaining that course-specific content comes from per-course skills, but since there are no parameters to document, the description appropriately avoids unnecessary detail.

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 is a 'GLOBAL methodology for building a Canvas ASSIGNMENT/LAB page' from a universal skeleton, giving a specific verb, resource, and scope. It distinguishes itself from per-course skills and sibling builders by framing itself as the global method, though it does not explicitly name alternatives.

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?

It explicitly says 'Use when building/updating any Canvas assignment or lab page,' providing clear usage context. It also references per-course skills as customizers, implying when those would be preferred, but does not give explicit exclusions or alternatives beyond that.

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