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

Annotations already declare this is a write (readOnlyHint=false), non-destructive, idempotent, and closed-world, so the safety profile is covered. The description adds only the vague phrase "privacy-filtered project metadata" and does not explain the retry/idempotency behavior that the idempotencyKey parameter implies, nor what happens on conflict or what data is persisted.

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 sentence, but it is poorly front-loaded and self-contradictory ("Update hosted create finding"), which forces the reader to parse twice. Brevity here reflects under-specification rather than effective conciseness.

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 five-parameter mutation tool with a nested object, required idempotency key, and no output schema, one ambiguous sentence is inadequate. Nothing explains the create-vs-update semantics, idempotency behavior, or how the nested details object is used, leaving the agent under-informed about a write operation.

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%, so the baseline is 3; the schema already documents projectId, sessionId, executionId, idempotencyKey, and the nested details fields in detail. The description adds no parameter meaning beyond that—"privacy-filtered project metadata" does not clarify any of the five parameters.

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 description opens with "Update hosted create finding," which mixes the verbs update and create and directly conflicts with the tool name create_finding. "Hosted" and "privacy-filtered project metadata" are undefined jargon, so an agent cannot confidently tell this apart from its sibling update_finding. It essentially restates the name with a contradictory verb rather than stating a specific verb+resource.

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 is given on when to use create_finding versus update_finding, promote_insight_to_finding, or list_findings, despite those siblings existing in the same namespace. The sentence provides no context or exclusions, leaving the choice entirely to inference.

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