list_group_ransomnotes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful scoping ('for one group') and output semantics ('identifiers'), but does not disclose availability, rate limits, or other behavioral details. No contradiction with 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 short, front-loaded with the primary action, and every sentence earns its place: what it lists, how the output is consumed, and the argument definition. There is no redundant prose.

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 low-complexity, single-parameter tool with a read-only annotation and an output schema, the description is complete. It explains the purpose, the argument semantics, and the intended follow-up call, which is all an agent needs to invoke it correctly.

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 0%, so the description carries the full burden for the single parameter. It defines group as a 'Group name' and gives concrete examples ('lockbit3', 'clop'), making the required string actionable. This is exactly the compensation needed for a schema that only provides the title 'Group'.

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 states a specific verb and object: 'List the ransom note identifiers available for one group.' It clearly scopes the tool to one group and distinguishes it from the content-reading sibling get_ransomnote by noting that the output is identifiers, not content.

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 clear downstream instruction—feed a returned name to get_ransomnote—and implicitly defines the use case: enumerate IDs for a group. However, it does not explicitly contrast with the sibling list_ransomnote_groups or say when not to use this tool.

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