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

The annotations already establish that this is a safe read-only operation. The description adds valuable behavioral context: it returns a link and the user must complete the connection themselves in Feedlio's dashboard, explaining why direct connection is not possible.

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 focused sentences with no wasted text. It front-loads the key constraint and then states exactly what the tool returns.

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 link-generation tool, the description covers the essential workflow: why direct connection is impossible, what the tool returns, and who completes the action. Schema and annotations fill in the remaining structural details.

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 schema fully documents the single optional platform_slug parameter, including its purpose. The description does not add parameter-level details beyond that, which is acceptable given 100% schema coverage but limits the score to the 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 specific verb and resource: it returns a dashboard link rather than performing the connection itself. It clearly explains the tool's role, though it does not explicitly differentiate itself from siblings like list_social_accounts.

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?

It gives clear context for when this tool is needed: connecting a social account requires an OAuth popup that cannot be driven from a chat call. It does not name alternative tools or explicit exclusions, so it falls short of a perfect usage score.

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