list_group_negotiations

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

Annotations already declare the operation as readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It adds context by listing the metadata fields each entry carries and cross-references get_negotiation, but it does not disclose behavior for unknown groups, empty results, pagination, or ordering.

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 core action stated in the first sentence. The metadata breakdown and argument documentation each serve a clear purpose, and there is no filler or redundant content.

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 a simple one-parameter, read-only tool with an existing output schema, the description covers the purpose, the argument, and the key output fields. It does not elaborate on error cases or empty results, but those are not critical given the low complexity and the annotations.

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%, so the description carries the full burden for parameter meaning. It defines 'group' as 'Group name' and provides a concrete example ('lockbit3'), which is sufficient for an agent to construct a valid call. No further format constraints are needed for this single free-text parameter.

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 and resource: 'List negotiation chats for a group with ransom and outcome metadata.' This makes the tool's purpose clear and distinct at a glance. However, it does not explicitly differentiate itself from sibling tools such as list_negotiation_groups or get_negotiation.

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 a useful parameter example ('lockbit3') and notes that the returned id should be passed to get_negotiation, which provides some downstream routing. It does not state when to use this tool versus list_negotiation_groups or other list-related siblings, nor does it mention prerequisites or exclusions.

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