Api organisation objectives partial update

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true, but the description adds nothing — no mention of what fields are mutated, partial-update semantics, permissions, or side effects. No contradiction, but zero added value beyond structured data.

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?

It is a single token with no structural waste, but this is under-specification rather than conciseness. Nothing is front-loaded because there is nothing to front-load.

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 mutation tool with no output schema, an untyped body parameter, and only annotation-derived safety hints, the description is completely inadequate — an agent cannot determine what a partial update accepts or changes.

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 0% and the description provides no parameter information whatsoever. The 'body' parameter is an untyped free-form object with no hints about acceptable fields, so the description badly needs to compensate and does not.

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 is literally the operation ID repeated verbatim ('api_organisation_objectives_partial_update'), which restates the name rather than explaining it. It conveys no verb, resource scope, or semantics beyond what the tool name already encodes. It is a tautology.

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 at all on when to use this tool, when not to, or how it differs from siblings like ciso_assistant_api_organisation_objectives_update (full update) or _object_retrieve. An agent must infer everything from the name suffix.

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