create_course_section

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that this is a WRITE operation that 'creates data' and that the response includes the course contents with the new section. However, it does not disclose potential authorization needs, rate limits, or side effects beyond creation.

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 concise, using three lines. The inclusion of the endpoint path and emoji is somewhat unnecessary but does not hinder clarity. It front-loads the purpose and avoids extraneous details.

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?

The tool has no output schema, but the description mentions the response includes course contents with the new section, partially addressing return value. However, given the complex nested object in the body parameter and the lack of details about the body, the description is not fully complete for agents to invoke correctly without additional context.

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 provides 'Course Id' for the id parameter but the body parameter description is hidden ('You do not have permission to view this reference'). The tool description does not explain the body structure or provide example values. With 100% schema coverage but the body effectively undocumented, the description adds no clarity beyond what schema already offers.

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 'Creates a new course section in the course' providing the specific verb and resource. The endpoint '/v2/courses/{id}/sections' further clarifies the action. This differentiates it from sibling tools like 'create_course' which creates a whole new course.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or comparisons to other tools like update_course_section (if it existed). The agent must infer usage solely from the tool name and siblings.

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