get_homework

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

With no annotations, the description responsibly identifies a key behavioral constraint: results come from 'recent timeline notifications,' not a general assignments store. However, it does not clarify the recency window, authentication needs, or what happens when no matching notifications exist.

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?

A single sentence with no filler; the verb, object, and source are stated directly. The source qualifier 'recent timeline notifications' earns its place by narrowing the tool's behavior.

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 tool with no output schema and no annotations, a one-line description is thin: it omits the meaning of the subdomain parameter and any expectations about return data. An agent could select it, but would have to guess about input and result semantics.

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 single parameter 'subdomain' has zero schema documentation and the description never mentions it. The name is somewhat self-explanatory, but the description adds no meaning about optionality, format, or how it affects the request.

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?

States a clear action and object: 'Get homework assignments' with a specific source, 'recent timeline notifications.' This separates it from broader siblings like get_assignments and get_notifications, though the distinction is implicit rather than explicit.

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 when-to-use guidance or alternatives are mentioned. The phrase 'recent timeline notifications' implies a context, but the description never tells an agent when to choose this over get_assignments or get_notifications.

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