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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the login requirement, the fact that execution happens in the user's Chrome extension rather than in ChatGPT, and the nature of the return (install link plus the right tool page). It does not mention any rate limits or failure modes, so 4 rather than 5.

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?

Three tight sentences with the purpose front-loaded, followed by the rationale and the call trigger, then the return value. No filler, no repetition of the title or annotations.

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 states what is returned (install link and the relevant tool page), and the annotations cover the safety profile, so nothing essential is missing for invocation. The only gap is that the "other" platform value has no described behavior, which is a minor incompleteness.

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% and the platform enum is documented, so the baseline is 3. The description adds value by enumerating what data each platform value covers (Instagram comments/followers/following/posts, LinkedIn connections), helping the agent reason about the enum. The "other" enum value is left unexplained, preventing a 5.

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 purpose: explaining how to export Instagram data (comments, followers, following, posts) or LinkedIn connections via Lection. It clearly positions this as an informational/how-to tool rather than a scraper, which separates it from sibling extraction tools like youtube_comments. It does not name a specific sibling to contrast with, so it falls just short of the top mark.

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?

"Call this whenever the user asks for Instagram or LinkedIn data" is an explicit, unambiguous trigger condition. It also explains why the flow differs (login required, runs in the user's own browser via the extension rather than inside ChatGPT). No when-not-to-use or explicit alternative-tool routing is given, so it is a strong 4 rather than a 5.

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