Create Catalog Entity Property

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

Annotations already disclose that this is a non-read-only, non-destructive, non-idempotent, open-world operation, so the safety profile is covered. The description adds important behavioral context by marking the endpoint deprecated and naming replacement pathways, though it does not discuss permissions or side effects beyond that.

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 two sentences with the deprecation warning front-loaded, followed by the core action. There is no wasted text, and the most important use guidance appears first.

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?

Given the tool has a rich nested input schema, annotations, and an output schema, the description is mostly complete: it clearly marks the tool as deprecated and names alternatives. The main gap is that it does not clarify the nested `data` payload semantics, but the schema covers much of that structure.

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 the description adds essentially no parameter detail beyond "from provided data." It does not explain the nested `data.attributes` structure, required keys, or the catalog field value limit, leaving the schema to carry the burden without compensating prose.

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 Entity Property." It also flags deprecation and points to replacement approaches, but it does not explicitly distinguish this create tool from sibling tools such as update_catalog_entity_property or create_catalog_property beyond the name.

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?

It explicitly says the endpoint is deprecated and directs callers to use the `fields` attribute on catalog entities or native catalog endpoints instead. This gives clear when-not-to-use guidance and names concrete alternatives.

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