Make something happen in a vendor's app

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

Annotations already declare it is a mutating, open-world, non-idempotent operation, so the bar is lower; the description still adds real context beyond them: records are tagged with source 'control', webhooks fire before the call returns (a strong ordering guarantee agents would otherwise have to discover), and the response is the recorded events. It does not warn about duplicate side effects from repeat calls or auth prerequisites, which keeps it at 4.

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?

Extremely compressed and front-loaded: the core behavior comes first, then the valid actions, then record semantics and return behavior. Punctuation is dense and the vendor/action run-on takes a second pass to parse, but no sentence is wasted.

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 correctly covers the return value ('answers with the events it recorded') and explains side-effect timing plus source tagging. The only meaningful gap for a mutating, non-idempotent tool is whether repeated identical calls create additional fake records, which is left 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?

Schema coverage is 100%, so baseline is 3, but the description adds value the schema lacks: it enumerates the valid vendor/action combinations per vendor (including 'quickbooks has none') and clarifies that the free-form params object is simply 'how many'. Since no param has an enum in the schema, this enumeration is genuinely load-bearing.

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 title and first clause state the intent ('make something happen now, as if someone did it in the vendor's own app') and the description then enumerates the exact actions per vendor (jobber newClients/payInvoices; housecallpro newCustomers/completeJobs/invoiceJobs/payInvoices; quickbooks none). That enumeration pins down the resource far better than the abstract verb alone. It doesn't explicitly contrast itself with siblings like twin_webhooks or twin_changes, so it stops short of a 5.

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?

Usage is implied by 'now' plus the concrete action list, and there is a useful exclusion ('quickbooks has none'), which prevents a whole class of wasted calls. However, nothing says when to prefer this over siblings such as twin_webhooks, twin_changes, or twin_load_scenario, so the agent must infer the boundary.

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