moodle_deadlines

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered and the description does not need to repeat it. It adds that results include submission status, which is useful return-shape context, but says nothing about auth prerequisites, ordering, or whether this covers all courses or only enrolled ones.

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?

Two short sentences with zero filler. The purpose is stated first and the parameter explanation follows, so an agent gets the essentials in one pass.

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?

There is no output schema, so the description is the only source for what comes back, and it only says 'deadline list and submission status' without field detail. With one parameter and safety already covered by annotations, the definition is adequate to invoke the tool but thin on result expectations.

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 carry the single parameter — and it does, clarifying that days_overdue is how many days into the past to include, resolving the otherwise ambiguous name. It stops short of stating how 0 behaves or whether the value is clamped, which is a minor residual gap.

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 names the two things returned: a deadline list and submission status. That is a clear resource statement an agent can act on. It lacks an explicit verb and does not differentiate from siblings, though the sibling set (login, course, announcements, activity, download_file) is distinct enough that confusion is unlikely.

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?

Usage is only implied: an agent can infer this is the tool for upcoming/past Moodle deadlines. There is no explicit statement of when to use it, what it excludes, or whether authentication via moodle_login must happen first.

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