get_assignments

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

The description implies the tool is read-only via 'Get', but does not explicitly state it is non-destructive or disclose any behavioral traits like rate limits or authentication needs. With no annotations, the description provides minimal transparency beyond the action.

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 well-structured with a summary, Args list, and Returns line. It is concise but not overly brief; each sentence adds value. Minor redundancy could be trimmed, but overall efficient.

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 that an output schema exists (context signal true), the description need not detail return values. It adequately covers parameters and the return type 'JSON array of assignment items'. However, it lacks error handling or prerequisites, which would enhance completeness.

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 0%, so the description must explain parameters. It does so thoroughly: defines each parameter, provides defaults, lists valid values for 'event_type', and clarifies usage for 'school'. This adds significant meaning beyond the schema's titles.

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 'Get all assignments (homework, tests, exams, projects, etc.) from the last N days', which specifies the verb, resource, and scope. It distinguishes itself from siblings like 'get_homework' by covering multiple assignment types.

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 guidance on when to use this tool versus siblings (e.g., 'get_homework'). Does not mention when not to use it or under what conditions.

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