get_study_load

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the analysis purpose but does not disclose assumptions (e.g., current user, current semester), data freshness, whether it includes only assignments with deadlines, or any constraints on the analysis.

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 sentence of 12 words with no unnecessary details. It is front-loaded with the core purpose immediately clear. Every word earns its place.

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?

Despite having no parameters and no output schema, the description does not specify what the output contains (e.g., a list of weeks with assignment counts, heavy week labels). For a simple tool, this is a notable gap. The lack of output schema means the description should compensate, which it does not.

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 and 100% schema coverage, so the baseline is 4 per the calibration rule. The description adds no param information, which is appropriate since there are no parameters to document.

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-resource pair ('Study load analysis showing assignment distribution by week') and clearly distinguishes from siblings like weekly_review or get_course_progress by focusing on assignment distribution and identifying heavy weeks.

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 guidance on when to use this tool versus alternatives. The description implies usage for analyzing weekly assignment load but does not mention exclusions, prerequisites, or when to prefer sibling tools like weekly_review or get_course_health.

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