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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered elsewhere. The description does add one real behavioral fact — only 'active' insights are returned and results span all teams — but says nothing about ordering, whether dismissed items are excluded by definition, or what happens when limit is exceeded.

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?

Two front-loaded sentences with the scope stated first and the optional filters second. Slightly redundant with the schema's parameter descriptions, but nothing wasteful.

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?

No output schema exists, and the description never characterizes what an 'insight' contains, so an agent cannot anticipate the return shape. With zero required parameters, 100% schema coverage, and safety covered by annotations, the remaining gap is moderate but real.

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 tab enum, the limit range, and unseen_only are all fully documented in the schema. The description merely restates the filter options without adding format, default, or interaction details, which is the correct baseline-3 case.

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 and resource ('get active insights') plus the scope: the authenticated user's insights across all their teams. That scope does implicitly separate it from get-team-insight-summary-tool, but the sibling is never named, so differentiation is inferred rather than explicit.

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 optional tab filter and unseen_only flag hint at usage patterns, but there is no statement of when to choose this over get-team-insight-summary-tool or get-my-status-tool, and no exclusions. Usage is implied by the description rather than guided.

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