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

With no annotations, the description carries the burden and usefully discloses that each call costs 5 credits and that engagers are persisted to the post_engagements graph. It does not cover rate limits, pagination, or full return-shape details, but the cost and persistence side effect are significant behavioral context beyond the schema.

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 three tight sentences, front-loaded with the tool's purpose, followed by cost and persistence behavior. Every sentence adds practical information without repetition or filler.

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 two-parameter fetch tool with no output schema and no annotations, the description gives enough context to select and invoke it: what it returns, what it costs, and that results are persisted. It could still mention pagination or return limits, but the core invocation context is present.

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 the schema already documents both post_url and refresh. The description adds the notion of a 'single LinkedIn post' but does not elaborate on parameter formats or the refresh/cache behavior beyond what the schema provides.

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 uses a specific verb and resource: 'Fetch the people who reacted to a single LinkedIn post.' It clearly scopes the tool to a single post, which distinguishes it from sibling tools like linkedin_profile_reactions and linkedin_post_comments without needing to name them.

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 the tool's use case by stating it fetches reactors on a single post, but it does not explicitly say when to use this versus linkedin_profile_reactions, linkedin_post_comments, or other engagement tools. No exclusions or alternative-routing guidance are provided.

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