get_negotiation_chat

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds meaningful behavioral context: the Pro-tier requirement and API key prerequisite, and the dependency that `chatId` requires `group` to be set. It also clarifies that this is a read-only lookup over leaked data. No contradictions with annotations exist.

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 a single dense sentence that front-loads the core purpose and then packs in all three usage modes. It is efficient with no filler, but the sentence is somewhat long and could be split for readability. Still, every clause earns its place.

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 read-only, multi-mode lookup tool with an output schema, the description covers all necessary invocation patterns, the auth requirement, and parameter dependencies. Since an output schema already documents return shapes, no further return-value explanation is needed. The description is complete for safe and correct usage.

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, but the description adds value beyond the schema by explaining the parameter sequence and dependency: `group` is optional to list all groups, and `chatId` is only usable after calling with `group`. This goes beyond the schema's field-level descriptions, which only state the dependency, not the intended workflow.

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 clearly states the resource ('leaked ransomware negotiation chat logs') and the action ('Get'), and specifies the three distinct call modes (no args, group, chatId) that define its scope. This differentiates it from sibling tools like get_ransom_note and get_recent_victims by the exact data type it serves.

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 provides explicit step-by-step call patterns: no arguments lists available groups, adding `group` lists that group's chats, adding `chatId` reads the full thread. It does not explicitly name alternative sibling tools or state when not to use it, but the workflow guidance is unambiguous and sufficient for correct invocation.

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