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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value beyond that: per-platform rate limits (LinkedIn 30/hour and 100/day, Instagram 10/hour and 100/day) and the fact that quota is shared with likes, comments, follows and new chats. That quota-sharing detail is exactly the kind of budget information an agent cannot get from the annotations.

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, front-loaded with the resource and target, then the follow-up routing rule and quota caveat. The parenthetical return-field list is compact and informative rather than filler. Slightly dense with the rate-limit clause buried mid-sentence, but no wasted wording.

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?

No output schema exists, and the description does compensate by listing returned fields. But with four parameters at zero schema description coverage, an agent still lacks guidance on limit/cursor pagination and on what account_id represents, leaving a real gap for a tool that is likely paginated at 100 max per page.

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%, so the description must carry the load, and it only partially does: it hints that 'identifier' is a username (or person/company) and implies an account selection, but never explains account_id, limit, or cursor. Pagination and page-size behavior — the two parameters most likely to be misused — go completely unaddressed.

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?

States a specific verb and resource ('Recent posts') and scopes the targets precisely: a person or LinkedIn company, or an Instagram user by username. It also enumerates the return fields (id, social_id, text, counts, media), so an agent knows the shape of the result. It stops short of naming a sibling to distinguish itself from, e.g., list_own_posts.

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?

Provides one concrete routing rule: use the returned social_id for comments, likes and get_post_media, which is genuinely actionable chaining guidance. However, it never says when to prefer this over list_own_posts, list_company_pages, or list_user_comments, so the main selection decision among siblings is left implicit.

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