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

No annotations are provided, so the description carries the full burden. It implies a read operation ('Find') and discloses a platform limitation (LinkedIn), but it does not mention rate limits, auth requirements, pagination behavior, or what happens with no results. Some behavioral context is given, but significant gaps remain.

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 sentences, both purposeful and front-loaded. The first sentence states the action and scope; the second explains the use case and an exclusion. No wasted words.

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 tool with 3 parameters, no output schema, and no annotations, the description is incomplete. It explains the purpose but omits parameter semantics, return format, pagination, and error behavior. The agent would need to inspect the schema (which also lacks descriptions) or guess to call it 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?

The schema has 0% coverage and the description does not mention any of the parameters (q, platform, cursor). It lists platforms in prose but does not connect them to the platform parameter, nor does it explain what q or cursor mean. The agent gets no help from the description in understanding parameter usage.

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 uses a specific verb ('Find') and resource ('accounts') and enumerates the exact platforms (youtube, tiktok, instagram, x, reddit, threads). It also clarifies the use case: turning a person/brand name into a handle for other tools, and notes the LinkedIn exclusion, which differentiates it from generic search.

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 clear context for when to use it ('turning a person or brand name into the handle the other tools take') and an explicit exclusion ('LinkedIn has no profile search'). It does not name alternatives or state when not to use it, but the context is strong enough to guide selection.

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