update_course

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only says 'Update' and notes a required-field constraint; it does not mention permissions, reversibility, side effects, or what happens if no fields are provided. This is insufficient for a mutation tool.

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 concise sentence with no filler. The action verb and resource are front-loaded, and the field list is compact.

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?

With no annotations and no output schema, the description must provide comprehensive context. It fails to clarify update semantics, return values, error behavior, prerequisites, or authorization requirements. The enumerated fields and one constraint are not enough for a 7-parameter mutation tool.

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 description coverage is 0%, so the description must compensate. It lists field names already present in the schema, adding only the 'at least one field required' constraint. It does not explain valid values for lang, visible, or categoryid, nor the role of course_id beyond being required.

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 the tool updates a course and enumerates the specific updatable fields (fullname, shortname, summary, visible, lang, categoryid). This distinguishes it from sibling tools like update_section or create_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 implies this tool is for modifying existing course fields, but it does not explicitly state when to use it over alternatives or provide exclusion criteria. No mention of create_course, update_section, or conditions where a different tool should be used.

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