mdl_custom_lists_recent_activity

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

Annotations declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond the annotations; it does not disclose pagination behavior, ordering, rate limits, or what 'recent activity' actually contains. With annotations present the bar is lower, but the description still provides no extra behavioral context.

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 very short, but this is under-specification masquerading as conciseness. The single fragment lacks a subject and verb, so it does not effectively front-load useful information. It is neither wasteful nor helpful.

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?

Given the tool has two undocumented parameters, no output schema, and no annotations conflicting, the description is completely inadequate. It provides no information about what data is returned, how it is ordered, or how pagination works, leaving an agent unable to invoke the tool correctly with confidence.

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%, meaning the two parameters (page, limit) have no documentation in either description or schema. The description does not mention pagination or any parameter semantics, so it fails to compensate for the coverage gap. Baseline would be 3 if schema were rich, but here the description must carry the burden and does not.

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 'Custom Lists: recent activity.' essentially restates the tool name (mdl_custom_lists_recent_activity). It does provide a vague hint that it concerns recent activity in custom lists, but it lacks a specific action verb (fetch? list? summarize?). Among siblings like mdl_custom_lists_get_user_lists or mdl_custom_lists_popular, it fails to distinguish what 'activity' means or what resource is returned.

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, when-not-to-use, or alternative guidance is provided. An agent has no way to decide between this tool and siblings such as mdl_custom_lists_trending or mdl_custom_lists_featured, nor any condition that selects it.

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