get_unsubscribe_info

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

Beyond the readOnlyHint annotation, the description adds key behavioral context: it 'does not take any action' and the server 'never auto-fetches unsubscribe URLs.' This tells the agent exactly what side effects to expect and prevents overreach. 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 two sentences, front-loaded with the primary action, and every clause earns its place. There is no fluff or repetition of schema details, making it highly concise and well-structured.

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 one required parameter and no output schema, the description fully covers the return value possibilities (mailto, https, or both), the non-mutating behavior, and usage scenarios. It gives the agent everything needed to select and invoke the tool 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?

The input schema fully describes the only parameter, emailId, as a composite id from previous tool output. The description does not add extra semantic detail about the parameter, so it relies entirely on the schema. Per the rubric, with 100% schema coverage, a baseline of 3 is appropriate.

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 tool's function: reading the List-Unsubscribe header and reporting how to unsubscribe (mailto, https, or both). It uses a specific verb ('Read') and names the resource, and it distinguishes this from the sibling tool 'unsubscribe_sender' by explicitly noting it takes no action.

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?

Explicit usage guidance is provided: use before 'unsubscribe_sender' to see available options, or to pass an https link to the user/agent for manual opening. It also mentions the server never auto-fetches URLs, which clarifies when this tool is appropriate. This is a model of clear when-to-use advice.

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