list_assignment_enrollment_conditions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the HTTP verb GET, which implies a read-only operation with no destructive effects, and hints that pagination/filtering/sorting are supported via query parameters. However, it does not cover side effects, authentication or permission requirements, or how pagination behaves, and it provides no meaningful context beyond what "List" and "GET" already imply.

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 two sentences with zero wasted words. The action and exact endpoint are stated up front, followed immediately by a terse but complete parameter-placement instruction. Every sentence earns its place and the agent can scan it fast.

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 that an output schema exists, the description need not explain return values, and the core calling contract is covered: endpoint, route ID placement, and query usage. The main remaining gap is the unexplained `body` parameter; combined with the absence of sibling differentiation, a bit more context would help. Overall, however, an agent has what it needs to invoke the tool correctly in the common case.

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%, so the free-text description must compensate for three loosely-typed parameters. It partially does: it maps `path_params` to route IDs and `query` to filtering, pagination, sorting, and include values, which adds real meaning to the open schemas. The `body` parameter is never mentioned at all, leaving one of three parameters undocumented in both schema and description.

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 states a specific verb and resource — "List assignment enrollment conditions" — and pinpoints the exact endpoint `GET /assignments/{assignmentId}/enrollment-conditions`, leaving no ambiguity about what is returned. It is readily distinguishable from the similar sibling `list_assignment_enrollment_extras` because the resource differs (conditions vs. extras), though it does not call out that sibling by name. This is clear and precise, but falls short of the top score because the description never explicitly differentiates itself from related tools.

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 gives routing guidance — put route IDs in path_params and filtering/pagination/sorting/include values in query — which tells the agent how to fill the parameters. However, it never states when to prefer this tool over alternatives like `list_assignment_enrollment_extras` or when NOT to use it. Usage context is implied for a straightforward read/list operation, but explicit when/when-not guidance, as well as prerequisites such as needing the assignmentId, is absent.

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