initiative_manage

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

Annotations only supply readOnlyHint=false, so the description carries the burden: it says 'every action has explicit scope and effects' without stating what merge or delete destroy, whether they are reversible, or that they require confirmation. It also omits the replay/idempotency contract that the schema's request_id points to, and says nothing about expected_slot_revision concurrency behavior.

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?

Two short sentences with the action list front-loaded; nothing is padded. The closing sentence, 'Every action has explicit scope and effects', is vague boilerplate that asserts rather than informs.

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 six-variant mutation tool with destructive operations (merge, delete) and a concurrency token, the description omits irreversibility, permission/auth needs, and the replay contract, despite an output schema existing. An agent could call merge or delete without knowing the consequences.

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% and the oneOf variants already name every field (source/target, node, slot, expected_slot_revision). The description adds only the loose notion of a 'current-record slot' and otherwise paraphrases the action set the schema defines exactly.

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?

Enumerates specific verbs and resources: rename, merge, delete, attach membership, set/clear a slot. An agent immediately knows this is the mutating counterpart to the sibling 'initiatives' listing tool, though the description never names that sibling explicitly.

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 on when to choose this over siblings such as 'initiatives' or 'lifecycle', no prerequisites, and no when-not conditions. 'Occasionally set/clear a current-record slot' hints at rarity but not at any selection criteria.

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