patch-crm-v3-properties-objtype-var_var

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Update a property' reveals nothing about side effects, permissions, partial vs. full update semantics, immutability of fields, or error behavior. This is a complete absence of transparency.

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 three-word description is under-specified rather than effectively concise. A tool with 12 parameters and no annotations requires more explanation; the brevity sacrifices actionability and leaves the agent without critical context.

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 12 parameters, no output schema, and no annotations, this tool demands substantial contextual guidance. The description provides none of it—no return format, required field nuances, usage scenarios, or operational details. It is completely inadequate for reliable invocation.

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 100%, so the baseline score of 3 applies. The description adds no parameter meaning beyond the schema, but the schema does describe each parameter, even if some descriptions (e.g., 'Path parameter objectType') are minimal.

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 'Update a property' essentially restates the tool name (patch-crm-v3-properties-objtype-var_var) without adding specificity. It doesn't clarify that this updates a property definition or metadata versus updating a property value on a record, making it a tautology rather than an informative purpose statement.

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 such as get-crm-v3-properties-objtype-var_var or post-crm-v3-properties-objtype_objtype. There is no mention of prerequisites, context, or exclusions.

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