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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds real value on top, disclosing that it returns an authUrl, that a human must open it in a browser (interactive, out-of-band step), and that a Picorn access token is required. It does not cover link expiration or failure modes.

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?

Two short sentences, front-loaded with the core action, each carrying distinct information (what it creates, how to use the result, what it requires). No filler.

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?

With no output schema, the description correctly explains the return (authUrl) and the required auth. It leaves minor gaps (link lifetime, error behavior), but an agent has enough to invoke it and route the next step 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 description coverage is 0%, so the description should compensate but says nothing about the single 'platform' parameter. The parameter name plus its 8-value enum make intent self-evident, so this is minimum-viable rather than a serious gap.

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?

States a specific verb and resource: 'Create an OAuth link that connects a social media account to the user's Picorn account.' This clearly separates it from siblings like picorn_account_status (which it names) and the campaigns/editor tools.

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?

Gives a concrete workflow: hand the authUrl to the user for a browser, then check picorn_account_status. This routes the agent to the right follow-up tool. It lacks explicit when-not/exclusion guidance, so it falls short of a 5.

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