ghl_project_upsert_space_statuses

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

The description does add real behavioral context (full-replace semantics, no If-Match, removed keys persisting on tasks, scope requirements). However, it also states omitted groups and statuses are removed, which is a destructive update while annotations declare destructiveHint=false — an inconsistency that an agent could act on incorrectly. The remaining preamble (RBAC, lexorank, recurring owners, delete cascades) is not about this tool.

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 tool-specific section is tight and well structured with the destructive replace semantics front-loaded within it, but a large leading paragraph of general project-management/API boilerplate (lexorank, recurring task fields, delete cascades) is unrelated padding that delays the actual behavior.

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, the description covers full-replace semantics, the removed-key edge case, endpoint, version, and required OAuth scope. It is complete enough to invoke correctly, with the only gap being that response shape is undocumented (acceptable given no output schema).

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 baseline is 3, but the description adds meaning beyond the schema: 'key is the stable id; label is display text' and the distinction that status color is any hex while space/folder/list color must use palette swatches. That is useful semantic clarification not present in the schema text.

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 operative sentence 'Update Statuses / Replaces the whole space status set' gives a specific verb (replace/upsert) and resource (space status set), and it distinguishes from siblings like ghl_project_get_space_statuses. The opening paragraph is generic API boilerplate rather than tool-specific purpose, so the identity is clear but not front-loaded.

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?

'Send every group you want to keep — omitted groups and statuses are removed' is genuine usage guidance for how to call it safely, but there is no explicit when/when-not or named alternative (e.g., per-list status routes, the get-statuses sibling). Usage is implied rather than routed.

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