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

The description goes beyond the readOnlyHint annotation by explaining the data returned and the conditional behavior when comments_synced is false. It also tells the agent how to handle that case, which is useful behavioral context. It doesn't mention edge cases like pagination or rate limits, but the disclosed behavior is solid for a read-only analysis tool.

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 somewhat long but each sentence earns its place: it defines the output, gives usage context, tells the agent what to cover from the data, and handles a conditional sync state. It is well-structured and front-loaded with the core purpose.

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 there is no output schema, the description compensates well by enumerating the returned data (per-post stats, comment samples, headlines) and by explaining how to handle the comments_synced=false state. For a single-parameter read-only tool, the description provides everything an agent needs to call and interpret the tool 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?

Schema description coverage is 100% for the single post_count parameter, which already documents default and max values. The description does not add additional meaning about the parameter, so a baseline score of 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 identifies the tool as an engagement analysis of recent LinkedIn posts, specifying the returned data: per-post stats, comment samples, and headlines. It is distinct from sibling tools like get_my_linkedin_posts or search_linkedin_posts by focusing on analysis rather than retrieval, though it does not explicitly name or contrast with those siblings.

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 explicitly states when to use the tool: 'Use when they ask for an analysis of their recent posts, what people are saying about them, or who their audience is.' It also gives conditional guidance for comments_synced=false. However, it does not describe when not to use it or explicitly point to alternative tools.

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