Append a free-standing text note (not tied to a screenshot) to a review created by create_review. Use for context, steps taken, or a summary of findings between screenshots.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The note text (plain text or markdown). | |
| review | Yes | The review slug or URL from create_review. | |
| claim_token | Yes | The claim_token from create_review (authorizes the write). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is a non-read-only, non-destructive write. The description adds behavioral clarity by saying the note is appended and is free-standing, meaning it does not replace or attach to a screenshot. This is useful beyond the annotations.
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 description is two sentences with no filler. The first sentence states the core operation and scope, and the second gives concrete use cases, making it efficient and easy to parse.
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?
The description is complete for a simple append operation: it explains the purpose, when to use it, and how it differs from screenshot notes. No output schema exists, so return values need not be described, and the schema handles parameter details.
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?
The input schema covers all three parameters with descriptions, so schema coverage is 100%. The tool description does not add parameter-specific semantics, which is acceptable given the schema already documents review, claim_token, and text clearly.
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 uses a specific verb ('Append') and names the exact resource ('free-standing text note ... to a review created by create_review'). It also distinguishes itself from add_screenshot by explicitly noting the note is not tied to a screenshot, so an agent can select it without ambiguity.
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?
The description gives clear usage context: use for context, steps taken, or summaries of findings between screenshots. It does not explicitly name alternatives like add_screenshot or state when not to use the tool, but the 'not tied to a screenshot' phrasing provides useful guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: reviews (create/get/update/email/add content), inboxes (create/check), and playbooks (get). No two tools overlap in purpose, and descriptions reinforce the boundaries.
All tool names follow a consistent verb_noun snake_case pattern (add_, check_, create_, email_, get_, update_). The verbs clearly indicate the operation and the nouns indicate the resource, making the API predictable.
Nine tools is well-scoped for the server's purpose: covering review lifecycle, inbox support, and playbook retrieval without redundancy. Each tool earns its place in the QA/capture workflow.
The tool surface covers the full review lifecycle (create, append, retrieve, update, email) plus supportive inbox and playbook operations. Minor gaps like no explicit delete or list operations exist, but auto-expiry and share-link retrieval mitigate them.