get_course_activity

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

With no annotations provided, the description carries the burden. It clearly states the tool returns engagement metrics and implies read-only via 'Get', but it does not explicitly mention side effects, authorization, or rate limits. The clarification that it returns engagement metrics, not assignment data, adds behavioral context beyond the schema.

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 two sentences, front-loaded with the action, and contains no filler. Every sentence serves a purpose: purpose first, then clarification/alternative.

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 simple one-parameter read-only analytics tool with no output schema, the description provides sufficient context to understand what the tool returns and what it does not. It could mention output format or date range, but it is adequate for tool selection.

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 coverage is 100% (course_id is described as 'Canvas course ID'), and the description does not add extra parameter details. Baseline of 3 is appropriate since the schema already documents the only parameter.

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 uses a specific verb and resource ('Get daily page views and participation analytics for a course') and explicitly distinguishes itself from assignment data, making it clear what the tool does and how it differs from siblings like list_assignments.

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 states when not to use the tool ('not assignment data') and provides an alternative ('use list_assignments for assignment info'), giving the agent clear guidance on tool selection.

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