schoology_get_upcoming_events

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing: no read-only confirmation, no auth requirements, no note on whether events are user-scoped, section-scoped, or paginated. 'Get' weakly implies a read, but nothing beyond that.

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 short sentence with the resource and constraint front-loaded and zero filler. It is efficient, though its brevity is partly the reason other dimensions are thin.

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 low-complexity, one-parameter read tool with no annotations and no output schema, the description is minimally adequate but leaves open what an 'event' contains and what happens with the optional days parameter. Not misleading, but not complete enough to be confident.

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?

With one parameter at 0% schema description coverage, the description must compensate. 'Within 1 to 180 days' clarifies that the days parameter is a forward-looking horizon, but this value is largely mirrored by the schema's minimum/maximum, and the default behavior when days is omitted (it is optional) is left unexplained.

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 specific verb and resource ('Get upcoming Schoology events') plus a temporal scope, so an agent can tell it apart from generic activity tools like get_recent_activity. However it does not differentiate itself from the sibling schoology_get_calendar, whose scope is ambiguous relative to 'upcoming events'.

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?

There is no when-to-use guidance, no indication of when this beats schoology_get_calendar, and no exclusions or prerequisites. The only guidance is the implicit 1-180 day window, which is restated from the schema.

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