conversations_get_contact_unsubscription_status

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which cover the safety profile. The description provides no additional behavioral context beyond what annotations state — it does not describe the return format, the effect of omitting email, or any potential edge cases. Since the description adds no value beyond the annotations, it falls short of the lowered bar.

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 extremely concise, being just a short phrase. It is appropriately sized for a simple tool and contains no unnecessary wording. However, it is essentially a repetition of the title/name, offering no extra structural benefit, yet it is not verbose or bloated.

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 read-only tool with 3 parameters, and given that the schema covers all parameters and annotations cover safety, the description is minimally sufficient. However, there is no output schema, so the description does not hint at the return structure. The missing piece is the response format, which would help the agent understand what to expect, but the tool's low complexity keeps the gap modest.

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% (all parameters have descriptions), so the schema already documents the parameters. The description adds no additional parameter meaning. According to the rubric, when schema coverage is high, a baseline of 3 is appropriate, and this description does not exceed that baseline.

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 clear verb and resource: 'Get Contact Unsubscription Status'. It is specific enough to indicate the operation is fetching unsubscription status for a contact. It does not explicitly differentiate from sibling tools, but none of the siblings appear to perform the same function, so the purpose is unambiguous.

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 explicit instructions on when to use this tool versus alternatives, but the name and parameter schema make it the obvious choice for checking unsubscription status. Siblings are mostly unrelated (ad management, invoices, etc.), so the usage context is implicitly clear, yet no explicit when/when-not guidance is given.

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