moodle_notifications

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds nothing behavioral beyond that: no mention of pagination, ordering, recency window, or what unread versus read state means in the result. It does not contradict the annotations, but it contributes no context they don't already carry.

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?

It is a single short fragment with no filler, so it is compact and front-loaded. But brevity here comes from under-specification rather than discipline — a verb and a clause about what is returned would cost little and add much.

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 simple two-parameter read tool with annotations covering the safety profile, the content-type list is genuinely useful context. Still missing: the action performed, any parameter guidance, and result shape (no output schema exists to cover it), leaving real gaps for an agent deciding whether to call this or a sibling.

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 description coverage is 0% for two parameters (limit, unread_only), so the description must compensate and does not. 'limit' and 'unread_only' are relatively self-explanatory names, but the description never mentions either, nor any default (limit=20), ordering, or what 'unread' scopes to.

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 resource ('the bell-icon notifications') and enumerates the content types it carries, which helps distinguish it from siblings like moodle_announcements or moodle_deadlines. However, it is a bare noun phrase with no verb — it never says whether the tool lists, fetches, marks, or dismisses notifications. An agent must infer the action, so the purpose is only implied.

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 and no mention of alternatives, even though siblings such as moodle_deadlines (due dates) and moodle_announcements overlap with the content types listed here. The agent is left to guess whether notifications or those dedicated tools should be preferred.

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