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

With no annotations, the description carries the behavioral burden. It discloses the required permission ('Requires read:courses'), the result ordering, and returned fields. However, it does not mention pagination/limit-offset handling (beyond the schema), any access scoping rules, or potential absence of results when no filters are supplied.

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 sentences with zero filler. The core purpose and scope are front-loaded, followed by filters and a permission requirement. Every clause earns its place.

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?

Provides purpose, ordering, filters, and permission, which covers the essentials for a read-only list tool. Missing explicit pagination behavior (page size default, skipping) and a clear statement that all filters are optional, though limit/offset schema descriptions offer some guidance. No output schema exists, so the mention of returned fields ('student profile and lesson title') is useful but minimal.

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 40% (only limit and offset have descriptions). The description adds semantics for status, course_id, and lesson_id by labeling them as filters, which is helpful but does not explain each parameter's role in detail or that filters are optional. It partially compensates for the low coverage.

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?

States a specific verb ('List'), resource ('assignment submissions'), scope ('in the community'), ordering ('newest first'), and included data ('student profile and lesson title'). It clearly distinguishes from siblings like get_assignment_submission (singular fetch) and grade_assignment_submission (grading action).

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 mentions filtering by course_id, lesson_id, or status, which implies when to use those parameters, but it does not explicitly state when to prefer this list tool over the singular get_assignment_submission or provide exclusion criteria. Usage context is clear but alternatives are not addressed.

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