create_vocabulary

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

With no annotations, the description carries the transparency burden. It discloses the return format (JSON with status, name, schema, comment) and the default schema behavior, which is helpful. However, it does not mention permissions, side effects (e.g., overwriting existing tables), failure modes, or any irreversible actions, leaving some behavioral uncertainty 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 well-structured and concise: a one-sentence purpose, a bulleted Args section, a Returns section, and an example. Every part adds value, and the format is easily scannable for an agent.

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 description covers purpose, parameters, return value, and provides an example, making it fairly complete for a create-vocabulary tool. It lacks edge-case handling (e.g., duplicate names, null schema implications), but given the moderate complexity and presence of return format, it is sufficiently complete for typical usage.

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 description explicitly documents all three parameters: vocabulary_name, comment, and schema, providing meaning beyond the bare schema definitions. It clarifies defaults and purpose (e.g., 'default: domain schema'), compensating fully for the 0% schema description coverage.

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 states a specific action: 'Create a new vocabulary table for storing controlled terms.' This clearly identifies the tool's purpose and distinguishes it from siblings like create_table or create_catalog. The verb-resource pair is explicit and unique.

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 usage by its specific purpose (creating vocabulary tables) and provides an example, but it does not explicitly contrast with alternatives like create_table or state when not to use it. There is no direct guidance on choosing this over sibling tools, so usage is implied rather than explicitly directed.

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