stop_list_unsubscribe

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, but the description adds no further behavioral context. It does not clarify what the tool returns, whether authentication is needed, or any side effects, so the description offers no value beyond the structured metadata.

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 fragment of text, but it is under-specified rather than appropriately concise. It conveys only the endpoint and SDK parity, omitting key information about purpose and behavior, so it fails to earn its place as a useful description.

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 tool with no output schema and only minimal annotations, the description is far from complete. It does not explain what the tool does, when to use it, or what the response looks like, leaving the agent to infer everything from the name and endpoint.

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 100%, so all three parameters (limit, dry_run, cursor_next) already have descriptions. The tool description itself does not mention any parameters, but the baseline of 3 applies because the schema fully documents them.

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 is merely 'GET /api/v2/stop-list/unsubscribe (Python SDK parity)', which is a raw endpoint reference rather than a statement of what the tool does. It does not clearly specify an action on a resource, and it fails to distinguish itself from sibling tools beyond the endpoint path.

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?

No usage guidance is provided. The description does not indicate when to use this tool, what scenarios it is suitable for, or how it compares to alternatives like remove_stop_list_email or search_stop_list.

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