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

Annotations already establish this is a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds useful scope context — that results are limited to content LinkGPT itself has synced, and that sync status is included — but says nothing about how fresh the sync is, what happens when no account is connected, or how 'latest' is bounded.

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?

A single compact sentence with no filler, and the resource list is front-loaded. Its brevity is mostly earned, though the fragment structure means the reader has to supply the implied verb.

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 one-parameter read tool with rich annotations, this is close, but with no output schema the description must carry the return shape and instead leaves the response structure and the scope of the limit ambiguous. Adequate but with a clear gap an agent would hit on the first call.

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?

There is only one optional parameter and its schema description ('How many to return (max 50)') is fully covered, so the schema does the work. The description does not clarify the crucial ambiguity of whether limit caps connected sources or individual posts/videos/pages, which would have been genuinely additive.

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 enumerates the data returned (connected website/social accounts, sync status, latest posts, videos, pages) but reads as a noun phrase with no verb, so it never explicitly says it lists or retrieves anything. It largely echoes the title 'Connected sources and latest content' rather than differentiating itself from siblings like get_profile or get_citations.

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 statement of when to call this tool, no prerequisites (does a site need to be connected first?), and no mention of any sibling alternative. The agent must infer from the data listed that this is the entry point for 'what sources and content do I have'.

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