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

With no annotations, the description carries the full burden and does well: it discloses the data source (local library, no live pull), that it is free, that results are paginated, and that returned data includes full metrics and text. It omits specifics on return shape and any rate/permission constraints, keeping it just short of a 5.

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?

Front-loads the core purpose, then adds filtering scope, pagination, and alternatives in a tight sequence. Every sentence — including the cost/data-source note and the sibling routing — carries distinct, useful information.

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 an 11-param tool with no output schema and no annotations, the description covers data source, cost, pagination, filter axes, scope semantics, and alternatives. The only gap is a fuller picture of the returned 'full metrics' payload, but overall it is complete enough to call 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 coverage is 100%, so the schema already documents most fields. The description still adds conceptual value: it explains scope as a post_collections.id restricted to a collection and gives concrete examples (external profile, topic stream, curated set), and summarizes the filter axes (date range, post type, min engagement, text) that map to the params.

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+resource ('List a tracked profile's persisted posts') and immediately scopes it to the local library with 'no LinkedIn pull, free'. It distinguishes itself from both search_posts and linkedin_profile_posts by name.

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?

Gives an explicit entry condition ('when the caller already has a profile_id') and names two alternatives with their selecting conditions: search_posts for keyword/semantic search, linkedin_profile_posts for fresh pulls. Nothing is left to inference.

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