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

Annotations already declare the tool as readOnly and idempotent, so the safety profile is covered. The description adds that the tool returns an OAuth URL, which is useful behavioral context. However, it doesn't elaborate on what the URL is for, how it should be used, or any nuances (e.g., expiration, redirect behavior), so it adds limited value beyond the 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 a single, well-structured sentence that front-loads the action ('Get the OAuth URL') and specifies the target ('Pinterest account'). Every word earns its place, with no redundancy or irrelevant detail.

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 tool with no parameters, no output schema, and strong annotations, the description is largely complete. It fully states the tool's purpose and return type (OAuth URL). The only minor gap is that it doesn't mention any follow-up steps (e.g., user must open the URL to complete the connection), but this is not essential for tool invocation. Overall, it's sufficient for an agent to select and call 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 tool has zero parameters, so there is no parameter semantics to explain. The description doesn't need to add parameter information, and the baseline of 4 for zero-parameter tools is appropriate. The schema coverage is vacuously 100%.

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 a specific action (get the OAuth URL) and a specific resource (Pinterest account), making it immediately clear what the tool does. It distinguishes from sibling connect_* tools by naming Pinterest explicitly, so there's no ambiguity about which platform it targets.

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 implies the tool should be used when the user wants to connect a Pinterest account, providing clear context. However, it offers no explicit guidance on alternatives (e.g., other connect_* tools, checking existing connections via list_connected_accounts) or when not to use it, leaving the agent to infer from the name and context.

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