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

With no annotations provided, the description carries the full behavioral burden. It does disclose two useful traits: 'Merge' signals a partial update rather than a replace, and the server recomputes overall_complete when required items are DONE, which tells the agent not to set overall_complete manually. It omits permission requirements, reversibility, and the meaning of the enum states.

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 tight sentences, front-loaded with the operation and followed by the notable server-side side effect. Nothing is padded or redundant.

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 annotations, no output schema, and a high-complexity nested enum payload, the description covers the key behavioral quirk (auto-recomputation) but leaves the parameter vocabulary and permission/error context undocumented. It is adequate but noticeably thin for the tool's complexity.

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?

There is one nested 'status' object with 0% schema description coverage and no descriptions on the many enum fields. The description hints that overall_complete is derived, but it does not name the item fields, explain the eight enum values, or clarify the duplicated snake_case/camelCase keys, leaving the agent to reverse-engineer the payload.

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?

States a specific verb (merge) and resource (project-init progress fields) scoped to the current project, which clearly distinguishes it from the sibling get-project-init-status (a read). It does not name any sibling explicitly, but the read/write contrast is inferable.

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?

Usage is implied by 'merge ... progress fields for the current project,' so an agent can guess this is how you advance init progress. However, there is no explicit when-to-use guidance, no mention of prerequisites, and no routing against alternatives like get-project-init-status or mark-plan-items-implementation-done.

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