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

Annotations already declare this is a non-destructive, idempotent mutation (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description's only behavioral contribution is the vague phrase 'privacy-filtered project metadata', which hints at a data-handling constraint but never explains it. It does not state whether the source insight is consumed/converted or preserved, what permissions are needed, or what side effects occur.

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 front-loaded sentence with no padding, which is structurally fine. But the brevity comes at the cost of comprehensibility — the sentence is grammatically muddled ('hosted promote insight to finding') and its one content-bearing clause is vague.

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 6-parameter mutation with a nested object and no output schema, the description is far too thin. It omits prerequisites, the relationship between an insight and the produced finding, the role of idempotencyKey, and any notion of what the caller gets back. Annotations cover safety, but the operation's semantics remain unexplained.

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 nominally 100%, so the baseline is 3. However, the description adds nothing about the six parameters, and the schema's own descriptions are boilerplate identical strings ('Owned project ID returned by list_linked_projects') that are plainly wrong for findingId, sessionId and executionId — the description does not compensate for that confusion.

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 sentence 'Update hosted promote insight to finding using privacy-filtered project metadata' is a garbled restatement of the tool name rather than an explanation. It never says what an insight actually is, what the resulting finding contains, or how this differs from the sibling tools create_finding and update_finding. The verb ('Update' vs the name's 'promote') is even inconsistent, leaving the core action ambiguous.

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 when-to-use, when-not-to-use, or alternative routing guidance whatsoever. Given siblings like create_finding, update_finding and list_findings, an agent has no signal about when promotion is the correct path versus simply creating or updating a finding directly.

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