add_mesh_comment

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

With no annotations, the description carries the full burden, and it discloses only one behavioral fact: a Kiln Pro entitlement requirement, stated vaguely enough ("Everything in Free, plus...") to be ambiguous about whether this tool is gated. It says nothing about mutation effects, whether the comment is append-only, whether the target version must be locked or in a particular state, or what happens on failure.

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 useful content is one sentence; the remaining three lines are subscription upsell copy with a marketing URL that does not help an agent invoke the tool. The front-loading is good but roughly three-quarters of the text is waste.

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?

A six-parameter mutation tool with no annotations and no output schema needs the description to explain parameter intent, entitlement gating and success behavior. Almost all of that is missing, and the paywall text is too imprecise to tell an agent whether the call will be rejected on a free tier.

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 33% and only schema defaults for scope and anchor are documented; body, author, artifact_type and artifact_version_id have no descriptions anywhere. The description nods at two of these ("region-anchored" hints at anchor, "versioned artifact" hints at artifact_version_id) but adds no format, valid value, or default semantics to compensate for the gap.

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 opening sentence gives a specific verb and resource ("Add a region-anchored comment to a versioned artifact"), which is materially clearer than the bare tool name. However, it never distinguishes itself from the nearby comment siblings (list_mesh_comments, reply_to_comment, resolve_comment_thread, get_comment_thread), so an agent cannot tell from the text which of these to pick.

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 statement of when to use this versus reply_to_comment or resolve_comment_thread, and no prerequisites such as needing an existing artifact version or thread. The only conditional language present is a paywall notice, which is not invocation guidance.

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