Contenido de un curso

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

Without annotations, the description must carry the full behavioral burden, but it only describes what is returned. It does not disclose whether it is read-only, requires authentication, or any other behavioral traits. The agent gets no information about side effects or constraints.

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, clear sentence that effectively communicates the tool's purpose. While it could include more structured details, it achieves conciseness without 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 absence of an output schema and only one parameter, the description is too sparse. It does not explain the structure of the returned data (e.g., nested sections, fields per module), leaving significant uncertainty for the agent.

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 description does not mention any parameters. With 0% schema description coverage, the agent must rely solely on the schema, which only provides type and min value for courseId. No additional meaning or format hints are given.

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?

Clearly states it returns sections and modules (tasks, resources, forums) of a course, using a specific verb and resource. It distinguishes well from sibling tools like dutic_get_course_tasks (which only returns tasks) and dutic_list_course_materials (which may have different scope).

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 no guidance on when to use this tool versus alternatives. No mentions of use cases, prerequisites, or exclusions, leaving the agent to infer optimal usage from context alone.

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