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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds genuinely useful context beyond that: it accepts empty input, existing plan and access checks are retained for queries, and anonymous preview is restricted to a synthetic read-only demo dataset requiring sign-in for real projects.

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?

Four short sentences, front-loaded with the usage trigger, with no filler. Slightly dense with the auth/dataset caveats stacked at the end, but every sentence carries distinct 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 a zero-parameter UI-opening tool with full annotation coverage and no output schema, the description covers trigger, input expectation, and access/auth behavior. It does not clarify what the tool returns or whether the panel must be opened before querying, which would be the last missing piece.

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?

The tool takes zero parameters, so the baseline is 4, and the description correctly states that it accepts empty input, which keeps the agent from hunting for required arguments.

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 action on a specific resource: opening a compact project/view picker to explore a project's analytics alongside the conversation. It is clear what the tool does, but it never names or contrasts itself with the many sibling analytics_* tools, so an agent must infer that this is the interactive panel rather than a data query.

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?

"Use this when you want to explore an authorized project's analytics beside the conversation" gives a clear trigger condition, and the sign-in note implies the boundary for anonymous use. However, no alternative tools are named for agents who want raw data instead of the panel, so the routing guidance is contextual rather than explicit.

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