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

No annotations are provided, so the description carries full burden. It does not explicitly state that the operation is read-only, require authentication, or describe error handling for invalid slugs. The mention of 'vagas (mescladas com matrículas reais)' hints at data merging but lacks explicit behavioral disclosure.

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 sentence that efficiently conveys the tool's purpose and a key instruction. It is front-loaded with the main action and lists components without redundancy. No wasted words.

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 output schema, the description provides a comprehensive list of return fields. It also ties usage to a sibling tool. However, it does not describe the return structure or data format, which could be important for an agent. Still, it is largely sufficient for correct 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?

The input schema covers the single parameter 'slug' with a clear description and examples. The tool description adds value by instructing how to obtain the slug (via list_courses), which goes beyond the schema info. However, it does not elaborate on slug format beyond what the schema already provides.

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 clearly states it returns 'detalhe COMPLETO de um curso' and lists multiple specific components (description, modules, teachers, price, etc.). It distinguishes itself from sibling tool 'list_courses' by instructing the agent to use that tool to discover the slug.

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 explicitly advises 'Use list_courses pra descobrir o slug', providing a clear prerequisite and alternative. However, it does not explicitly state when not to use this tool or mention other siblings (e.g., check_availability) that may be relevant.

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