huddo_sync

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

No annotations exist, so the description carries the full burden; it does disclose the key behavioral fact that this modifies the local message store on this machine, and that full controls history depth and therefore search coverage. It omits whether existing messages are preserved or replaced, expected duration/network behavior, and idempotency, which matter for an unannotated mutating tool.

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?

A single front-loaded sentence with no filler; the scope qualifier comes first and the parameter caveat is appended compactly. Slightly dense phrasing ('for every room (or one room)') costs a bit of parsing clarity.

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 an unannotated three-parameter sync tool with no output schema, the description covers the core concept and the full-history trade-off. It leaves out what an agent would want before invoking: how long a full sync takes, whether it is safe to repeat, and whether partial failure is possible.

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 the baseline is 3; the schema already documents all three parameters including 'as' and 'room'. The description adds the consequence of 'full' (search coverage) that the schema does not state, but says nothing about the 'as' identity parameter, so the added value is modest.

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?

States a specific verb and resource: it updates/refreshes the messages stored on this machine, with scope qualifiers ('every room (or one room)'). An agent can infer this is a local cache sync rather than a server mutation, though it never contrasts itself with siblings like huddo_read or huddo_search.

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 clause 'full: true fetches the whole history so search covers it' implies when to set full (when you need search to be complete), which is useful implied guidance. There is no explicit when-to-use vs alternatives, no statement about when a plain sync suffices, and no mention of cost or duration trade-offs.

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