mdl_notifications_fetch

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds the genuinely useful constraint that host-configured MyDramaList authentication is required, but says nothing about pagination behavior or result shape.

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 fragments with no filler and the resource is front-loaded, but the size reflects under-specification rather than discipline. It is concise at the cost of being nearly content-free.

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 paginated list endpoint with zero schema documentation and no output schema, the description should at minimum explain that results are paged and what page/limit control. Annotations cover the safety profile, but the pagination contract is left entirely unstated.

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% and both parameters (page, limit) are undocumented in the schema, so the description carries the full burden for two params and provides nothing. It does not explain that page/limit drive pagination or what the defaults mean in practice.

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?

"Notifications: fetch" names the resource and the operation, but it is essentially a restatement of the tool name rather than a description of what fetching yields. It does not distinguish this from siblings like mdl_notifications_clear or mdl_notifications_clear_all, so an agent gets the gist but no differentiating detail.

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 guidance on when to use this tool versus its notification siblings, nor any note about pagination limits or typical result set. The only condition given is the authentication prerequisite, which is not usage routing.

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