patch-crm-v3-objects-objtype-objid_objid

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

No annotations are provided, so the description carries the full burden. It only states the requirement for a body parameter and shows an example, but does not mention whether this is a partial update, what the return value is, or any potential side effects. The example's 'body' wrapper also contradicts the schema's direct 'properties' parameter, which could mislead agents.

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 brief and front-loaded with the action and requirement. The example is practical and earns its place, though it is somewhat bulky. Overall, it is concise and readable.

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 no annotations and no output schema, the description is insufficiently complete. It does not explain what the update returns, whether it is partial or full, or any constraints. The bare example leaves out critical behavioral context for an 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 baseline is 3. The description adds an example showing the structure of properties, which is helpful, but the introduction of a 'body' wrapper not present in the schema creates confusion about the actual parameter structure.

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 says 'Update' and provides an example with properties, making it clear the tool updates an object's properties. However, it does not explicitly name the resource or distinguish it from similar tools like batch-update or create, so it lacks specific differentiation beyond the tool 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?

There is no guidance on when to use this tool versus alternatives such as batch-update or post (create). No context is provided about prerequisites or when this tool is appropriate.

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