learningsuite_get_course_submissions

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

With no annotations, the description carries full responsibility for disclosing behavior. It mentions the ordering (newest first) but fails to disclose pagination behavior despite having limit/offset parameters. The phrase 'all submissions' could mislead an agent into thinking it returns everything in one call, while pagination implies multiple calls may be needed. No information is given about return shape, permissions, or side effects (though 'get' implies read-only).

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 a single, front-loaded sentence with no wasted words. It conveys purpose and a key behavioral attribute efficiently, making it easy for an agent to parse quickly.

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 lack of annotations and no output schema, the description is incomplete for a tool with pagination. It doesn't explain what constitutes a submission, how to retrieve all pages, or what the response looks like. The tool is simple, but the description leaves significant gaps that could lead to incorrect invocation or incomplete results.

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 100%, with each parameter documented in the schema. The description adds no parameter-specific semantics beyond the schema, but it does provide useful context about ordering. Since the schema already handles the heavy lifting, a baseline of 3 is appropriate.

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 'Get all submissions in a course (newest first)' uses a specific verb and resource, clearly distinguishing it from sibling tools that focus on members, groups, modules, or other entities. The parenthetical adds precise ordering information, making the purpose unmistakable.

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 implies usage: when you need course submissions, this is the tool. However, it offers no explicit guidance about when to prefer this over alternatives or any exclusion criteria. No sibling tool is mentioned as an alternative, so context is only implicit.

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