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

With readOnlyHint=true and destructiveHint=false annotations already covering safety, the description adds useful behavioral context: aggregation across every team in the organization and the role gate. It does not contradict the annotations and provides value beyond the structured hints.

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 two sentences with no filler: the first sentence states the action, scope, and output KPIs, and the second states the access requirement. Important information is front-loaded.

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 read-only KPI retrieval tool with no output schema, the description covers what is returned, the aggregation scope, and role requirements, while parameters are fully documented in the schema. It is complete enough for an agent to call correctly, though it could add a pointer to related getOrgInsights* tools for fuller context.

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 orgId, startDate, and endDate including defaults and clamping behavior. The description does not add parameter-level detail, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'Get org-wide headline insight KPIs' and enumerates the exact metrics returned (run totals, success rate, distinct active agents and users), making the core purpose unmistakable. However, it does not explicitly differentiate from sibling tools like getOrgInsightsMetrics or getOrgInsightsUsageChart, which keeps it at a 4 rather than a 5.

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 role requirement (Admin, Executive, or Owner) gives a clear prerequisite, and the org-wide scope implies when this tool is appropriate. It does not name alternatives or state when to prefer getOrgInsightsMetrics or getOrgInsightsUsageChart, so usage guidance remains implicit rather than explicit.

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