update_document_class

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

No annotations provided, so description carries full burden. It includes a warning about potential property loss if the new class lacks matching properties. It also clarifies that only the class changes, not properties.

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 front-loaded with prerequisites in bold, followed by the main description, warning, and note. While each sentence adds value, it could be slightly more concise. Still clear and well-structured.

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 an output schema, so return value explanation is not needed. Description covers purpose, usage, side effects, and relationships with other tools. However, it does not mention error conditions or output format, but overall complete for the complexity level.

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 descriptions already cover both parameters (identifier as document id/path, class_identifier as new class). Description adds no extra semantic value beyond the schema. Schema coverage is 100%, so baseline is 3.

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 'Changes a document's class in the content repository.' The verb 'change' and resource 'document's class' are specific. Among siblings, there are tools like 'determine_class' and 'update_document_properties', making this tool distinct.

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?

Explicit prerequisites are provided: must call 'list_all_classes' or 'determine_class' first. It also clarifies when not to use it by stating it only changes class and directs to 'update_document_properties' for property updates.

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