document_add_schema_enum

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

No annotations are provided, and the description only states 'Set enum values', implying mutation. It omits behavioral details such as side effects, error conditions, permission requirements, or what happens if enum values already exist.

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 sentence and front-loaded with the verb, which is good for conciseness. However, it sacrifices completeness—it is too minimal given the tool's complexity, missing crucial context that would justify its brevity.

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 3 required parameters, no output schema, and no annotations, the description should provide more context about the operation's purpose, return value, and error handling. The minimal description leaves significant gaps 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?

Schema coverage is 100%, so the description does not need to add much. The description contributes no additional meaning beyond the schema property descriptions; it does not explain how the 'values' JSON array interacts with existing schema definitions or provide examples.

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 'Set enum values on a schema' clearly states the verb (set) and resource (enum values on a schema), distinguishing it from sibling tools like document_add_schema or document_add_schema_property. However, it could be more specific about the context (e.g., adding enum values to an existing schema's property).

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites (e.g., schema must exist, nodePath must be valid), or when not to use it. The description lacks any contextual usage advice.

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