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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. Description adds the filtering rule (start date >= today) and sort order, which shapes the result set. It doesn't mention pagination or the default limit's effect, but annotations cover the safety profile.

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?

Three tight sentences: scope, use-case examples, and alternative. Zero filler, front-loaded with the core constraint.

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?

Adequate for a simple filtered list with annotations covering safety and a fully-documented parameter. Minor gap: no indication of response shape or what happens when the horizon is empty, though no output schema exists to cover that.

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 100% and the sole parameter (limit) has a description with default and bounds. The description adds nothing parameter-specific beyond what the schema provides, so baseline 3 applies.

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+resource with scope ('turmas com data_inicio futura a partir de hoje') and ordering, distinguishing it from siblings like list_courses (all courses) and check_availability (real-time slots). An agent can identify exactly what this returns.

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 example queries it answers and names the alternative (check_availability) with the condition that selects it ('pra vagas em tempo real'). Clear when-to-use and when-to-use-else.

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