List Courses

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds value by detailing behavior of fields: slim returns only a subset, full includes all fields and include extras. It also clarifies that include is ignored when slim. This goes beyond annotations without contradiction.

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?

Concise, well-structured description with front-loaded purpose. Each sentence adds value: purpose, usage scenario, field projections, and filtering semantics. No fluff or redundancy.

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 5-parameter schema with enums and the absence of an output schema, the description covers purpose, parameter use, and interplay thoroughly. It omits pagination details, but for a list tool this is often implicit. The description is complete enough for correct tool selection and invocation.

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 covers all parameters, so baseline is 3. The description adds meaningful semantics: explains the trade-off between slim and full, the effect of include (ignored in slim), and the meaning of state vs enrollment_state. This enriches the agent's understanding of how to combine parameters effectively.

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?

Clear action verb and resource: 'List courses for the authenticated user' distinguishes from account-level listing. It also specifies the scope (authenticated user) and parameter roles, making it distinct from sibling tools like get_my_courses or list_account_courses.

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?

Provides explicit usage guidance for fields parameter: 'Use fields="slim" when enumerating... switch to "full" once you have identified the target.' Also explains state and enrollment_state filters. Does not mention alternatives or exclusions, but the guidance is actionable and clear.

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