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

The annotations already indicate this is read-only, idempotent, and non-destructive (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the safety profile is covered. The description adds the requirement that PostHog must be connected, which is useful context. However, it does not mention any pagination or return format details, but since annotations cover safety, the description adds some value without contradiction.

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 at two sentences, front-loading the main purpose and what it shows. It avoids unnecessary detail and is easy to scan. The only minor point is that it could be even more specific about usage, but it is efficient overall.

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 it's a read-only list tool with a simple schema and annotations covering safety, the description covers the essential context: what it lists, what it shows, and the prerequisite of PostHog being connected. There is no output schema, so return format is not documented, but that's a minor gap for a list tool. The description is adequate for an agent to call it 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 describes all three parameters (limit, search, companyId). The description does not add extra meaning beyond what the schema provides. Baseline 3 is appropriate because the schema handles parameter documentation, and the description doesn't add significant value.

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 lists saved insights in PostHog and what it shows (names, types, links). It's distinguished from related posthog tools by mentioning 'insights', but not explicitly compared to siblings like posthog_list_events or posthog_query_trends. Verbs and resource are clear, making the purpose understandable.

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 listing saved insights but does not explicitly state when to use this tool versus alternatives like posthog_query_trends or posthog_list_events. It does note the prerequisite that PostHog must be connected, which provides some context, but there is no explicit when-not or alternative guidance.

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