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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false, so the safety profile is covered. The description adds the specific API endpoint (profileUpdatesV2) and mentions pagination, but doesn't disclose details like rate limits or that results might be truncated. It adds some value beyond annotations but not extensive behavioral insight.

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?

The description is concise and front-loads the core purpose, mentioning the endpoint and pagination. It is efficient with two clauses, but could be slightly more structured (e.g., separating usage from pagination). Still, it is appropriately sized for an API reference.

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?

Given the tool has an output schema and complete parameter documentation, the description is adequate but not fully complete. The output schema likely explains return values, but the description doesn't mention any nuances like how to handle errors or the maximum start value. It is sufficient for basic use but lacks guidance on edge cases.

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%, so all parameters are already documented in the schema with descriptions. The description adds no additional semantic meaning to parameters beyond what the schema provides. It does mention pagination with start/count, which aligns with the schema, but doesn't add new information. Baseline 3 is appropriate.

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 clearly states the tool retrieves recent posts from a LinkedIn member, using a specific API endpoint (profileUpdatesV2), which distinguishes it from similar tools like scrape_my_posts or create_post. It is specific about the resource (member posts) and the action (get), though it could be more explicit about it being read-only.

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 implies usage for retrieving a member's posts knwoing their LinkedIn ID or URL Committed, and mentions pagination, but does not contrast with alternatives like scrape_profile or list_connections. It lacks explicit guidance on when to use this instead of sibling tools, leaving the selection to the agent's judgment. Context signals (annotations) indicate read-only, but no exclusions are stated.

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