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

With no annotations provided, the description must carry the burden of behavioral disclosure. It only provides a noun phrase ('Social Links') rather than an explicit statement that it returns or retrieves data. There is no mention of safety, side effects, or limitations, which is insufficient for a zero-annotation tool.

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, compact phrase with no filler words. It provides a useful summary in minimal space. It could be improved by adding a verb or input description, but conciseness itself is well-served.

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?

Despite having an output schema, the description leaves the query parameter completely undefined and does not state the expected input format or the list of supported platforms. An agent lacks enough information to confidently use the tool, making it incomplete for correct invocation.

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%, and the description does not explain the purpose of the 'q' parameter. An agent cannot determine that 'q' is a username or handle from the text alone, making the tool practically uninvocable without external knowledge.

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 'Direct profile URLs across 20 platforms', which conveys a specific resource and scope. It distinguishes itself from specialized platform tools like reddit_user or github by implying an aggregation across multiple platformstar. However, it omits a clear action verb and does not explicitly state that it takes a username as input, leaving slight ambiguity.

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?

There is no guidance on when to use this tool versus other social-adjacent tools (e.g., username, reddit_user, bluesky). The description does not mention alternatives or exclusions, so the agent is left to infer use cases.

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