my_recent_uploads

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

With no annotations, the description fully discloses that the tool is read-only, defines the parameter behavior (hours, default 24, <1 treated as 1), explains the return structure grouping by import source, and notes the dual pipeline semantics. Missing details on pagination or limits for results.

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?

The description is well-structured with sections for purpose, usage, parameter, return format, and a note. It is front-loaded with the main verb and resource. While slightly lengthy, every sentence adds value and uses formatting (emojis, bold) for clarity.

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?

The description covers the parameter, return structure with three object types, grouping, and a view URL. It explains the import_source prefixes. However, it does not mention behavior when no results exist or if hours exceeds some maximum.

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% (no parameter descriptions in schema), but the description explains the 'hours' parameter: it's a time window with default 24 hours and behavior for values less than 1. This adds meaning beyond the schema's type and default.

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 clearly states the tool retrieves recent uploads (questions, papers, lecture fragments) for the logged-in teacher. It uses specific verbs like 'retrieve' and 'group by batch', and distinguishes from sibling tools like search_questions by noting it's DB read-only and doesn't rely on stem keywords.

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?

The description provides a clear use case: after MCP recording the teacher wants to quickly check what was just uploaded. It specifies the hours parameter and default behavior. However, it does not explicitly exclude use cases or compare to similar tools like list_lecture_docs.

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