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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, and the description's "Read-only" merely restates that. It adds nothing about what a sync actually does — whether it triggers an external fetch, how long it may take, whether it can rate-limit, or what state changes indirectly occur under openWorldHint.

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?

Two short sentences with the action up front and no filler or redundancy in phrasing. The brevity itself is not the problem — the missing content is scored under other dimensions.

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 three-parameter tool with a nested object, no output schema, and zero schema descriptions needs the description to explain the opaque "extra" payload and the semantics of syncing. Nothing about the outcome, idempotency behavior, or return value is conveyed beyond the annotation flags.

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 description coverage is 0% across three parameters, so the description carries the full burden and provides nothing. account_id and attendee_id are guessable from their names, but the nested "extra" object has no documented meaning anywhere in the definition.

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?

"Sync chats for an attendee" names a verb, a resource, and a scope, so the domain is identifiable. However, "sync" is ambiguous — it does not say what is synced from where or what the effect is on the stored chats — and nothing distinguishes it from the sibling sync_chat or from list_attendee_chats.

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 only guidance is "Read-only," which is a safety statement rather than a when-to-use rule. There is no indication of when to choose this over sync_chat, list_attendee_chats, or get_attendee, and no stated prerequisites such as a connected account or an existing attendee record.

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