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

Annotations already declare the operation read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds useful context about the formats mode returning accepted URL formats per platform, but it does not describe the default response shape, ordering, or any other behavioral detail.

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 very short and front-loads the core resource before the parameter instruction. Every word earns its place with no repetition or 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?

For a simple read-only tool with one optional boolean parameter, high schema coverage, and safety annotations, the description is largely sufficient. It could be slightly more explicit that the default call returns the list of social links, but the tool name, title, and description together make this inferable.

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 100%, so the schema already documents the 'formats' boolean. The description rephrases it as 'accepted URL format per platform', which adds slight clarity, but it does not provide meaning beyond what the schema's 'known platform URL prefixes instead' already conveys.

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 identifies the resource as 'the creator's social links' and mentions the format toggle, so an agent can infer this is a read/list operation. However, it lacks an explicit verb such as 'retrieves' or 'lists', and it does not explicitly distinguish this from the sibling add/remove social link 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?

The description gives no guidance on when to use this tool versus split_add_social_link or split_remove_social_link. The only usage instruction is 'Pass formats: true', which is parameter guidance rather than tool-selection guidance.

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