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

Annotations already flag readOnlyHint=false and destructiveHint=true, and the description merely restates that the tool edits/configures a note without explaining what is overwritten, whether changes are reversible, or what side effects occur. It adds little behavioral context 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 compact and front-loaded with the action, using just two sentences with no filler. The second sentence is of questionable usefulness, but the overall structure is efficient.

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?

An update tool with 7 optional-looking parameters, a nested settings object, and no schema documentation is severely underdescribed. An agent cannot reliably determine which identifiers are required or how settings should be structured; the output schema does not compensate for missing input semantics.

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?

With 0% schema description coverage and 7 opaque parameters, the description should clarify at least the core fields. It only implies that the 'note' parameter is the editable content; id, jid, groupJid, limit, offset, and settings remain unexplained.

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 first sentence names a specific action ('editar/configurar') and a specific resource ('note no painel 9bot'), so an agent can infer this tool mutates a group note. It does not explicitly contrast with siblings like groups_note_delete or groups_settings_update, but the action is clear enough.

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 usage guidance is 'use when the user asks for groups, even with incomplete terms or synonyms,' which is overly broad and potentially misleading because a request for groups would more naturally map to groups_list or groups_get. There is no mention of when to prefer this over groups_note_delete or groups_settings_update, and no exclusions are stated.

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