list_posts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety is covered. The description adds two things not in the annotations: the default ordering (newest first) and a data-visibility constraint tied to consent that determines which posts this tool can even return.

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 short sentences, front-loaded with the core purpose and followed by the caveat. The consent sentence is slightly awkwardly worded ('after the user's consent'), but nothing is wasted.

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 an output schema present and full parameter documentation in the schema, the description needn't explain return values. It covers purpose, ordering, and the visibility caveat; only a note on pagination behavior or whether results are scoped strictly to the authenticated user is missing.

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%, with limit, query, since, and offset all documented in the schema, so the baseline is 3. The description's 'newest first' implies the sort order the offset/limit operate over but adds no syntax or format detail beyond the schema.

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 ('List the user's LinkedIn posts') plus a result ordering ('newest first'), and explicitly names the sibling that owns a subset of the data (get_recent_activity). An agent can distinguish this from the other list/search siblings without opening a schema.

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 an explicit when-not rule: posts made after the user's consent may only appear in get_recent_activity, which routes the agent to the right alternative. It stops short of covering the broader choice against search_messages/search_connections, but the key exclusion is stated.

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