Create Catalog Property

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

Annotations already disclose that this is a non-destructive, non-idempotent write operation in an open-world context. Beyond that, the description only says it returns a 'catalog_properties type' and adds no details about creation behavior, uniqueness constraints, required fields, or side effects.

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 very short and front-loaded, with no wasted clauses. However, its brevity contributes to under-specification for a nested-object creation tool.

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?

For a nested-object mutation with open-world behavior and no output schema, the description is too sparse. It does not explain required fields, valid kinds, catalog scoping, uniqueness behavior, or what the returned catalog property contains.

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 only 50% and there are nested parameters, but the description adds no parameter meaning. It does not explain catalog_id, the data wrapper, or the required nested attributes such as name and kind, leaving the schema to carry the burden.

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 verb and resource: 'Creates a new Catalog Property.' It is clear what the tool does, but it does not distinguish this from closely related sibling tools such as create_catalog_entity_property or update_catalog_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?

The description provides no guidance about when to use this tool, prerequisites such as needing an existing catalog, or how it differs from alternatives like create_catalog_entity_property and update_catalog_property.

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