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

Annotations only declare the safety/mutation profile (readOnly=false, destructive=false, idempotent=false), so the description's additions are valuable: reporting 'sent' awards Stars (a side effect), the operation is Free, and the replyUrl must be the user's own reply rather than the founder's post. It does not address what happens if the same stage is reported twice, which matters because idempotentHint=false.

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?

Four short sentences, front-loaded with the primary action, then the constraint on replyUrl, then stage definitions. Dense but every sentence carries information; no filler or repetition.

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 covers cost (Free), the reward side effect (Stars), and the stage vocabulary, which is enough to call the tool correctly. It leaves the repeat-reporting/non-idempotent behavior and error handling on an invalid replyUrl unstated.

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?

Beyond the schema's terse 'Required for 'sent'', the description adds the semantic constraint that the URL must point to the user's own reply, not the founder's post. It also assigns meaning to each enum value ('replied' = the founder answered), which the schema enum alone does not convey.

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 'Move a deal forward' is a clear verb+resource, and the enumerated stage transitions ('sent', 'replied', 'call_booked', 'closed_won', 'lost') make the specific function unambiguous. It is distinguishable from read-side siblings like get_scout_deals and claim_deal, though it never names an alternative explicitly.

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?

It gives conditional usage rules: replyUrl is required for the 'sent' stage, later stages are 'private pipeline steps', and the guardrail 'Only report what the user tells you happened' constrains when to call it. It stops short of naming a sibling tool to use instead.

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