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

Goes well beyond the annotations (which only flag the write + destructive + closed-world profile): it discloses partial-update semantics ('omitted fields are left alone'), idempotency ('nothing duplicates'), per-item isolation ('a failed item doesn't stop the rest'), the 100-item cap, and the needs_confirmation approval flow where one approval covers the batch. This is unusually rich behavioral disclosure.

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?

Dense but front-loaded — the core upsert action leads, followed by matching semantics, side effects, and confirmation behavior. Parenthetical and em-dash clauses pack multiple facts per sentence, which is efficient though slightly heavy.

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?

With no output schema, the description still explains the return shape (one result per item: created/updated with key, or failed with reason) and the confirmation path. For a batched mutation tool this covers everything an agent needs to call and interpret it.

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 67% and the description closes gaps: `url` is the match key mirroring a GitHub/Linear/Jira ticket, PR or doc; omitted fields are left untouched; statuses are referenced by name via compass_statuses_list. It does not explain `workspace` or `approvalId`, but those already carry schema descriptions.

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 pair (create or update) and resource (changes), plus scope: up to 100 per call, each matched by `url`. The upsert-by-url framing is unambiguous and no sibling tool operates on changes, so an agent can select this without opening the schema.

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?

Gives clear operational context: run again with the same urls to keep Compass in step, summarize before calling, and use compass_statuses_list for status names. It does not name a when-not-to-use case or an alternative tool, but no overlapping sibling exists, so the routing guidance is effectively complete.

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