detalle_cursada_docente

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

No annotations are provided, so the description carries the burden. It describes the output structure (metadata + categorized classes) but does not disclose side effects, authentication needs, or other behavioral traits. Since it's a detail tool, it's implied read-only, but that is not explicitly stated.

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, focused sentence that states the resource, source, and output structure without unnecessary 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 tool's simplicity (one parameter) and the presence of an output schema, the description provides sufficient information about the purpose and output structure. It doesn't cover edge cases or prerequisites, but for this level of complexity it's adequate.

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 schema has a single `url` parameter with no description. The tool description compensates by indicating the URL should be from `zona_clases/home/<hash>`, providing semantic context for the parameter.

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 identifies the tool as providing details of a cursada from a specific URL path, including metadata and classes grouped by category. It distinguishes from sibling tools like detalle_mesa_docente by specifying the course context and URL source, though the verb is implied rather than explicit.

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 a clear context: it is for retrieving details of a course from the zona_clases/home/<hash> URL. It does not explicitly mention alternatives or when-not-to-use, but the context is specific enough to infer the use case.

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