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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds meaningful context beyond the annotations by clarifying that the counts are aggregate and not unique-investor identities or diligence readiness scores, which prevents misinterpretation of the returned data.

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 short sentences with no filler. The first sentence front-loads the action and metrics, and the second sentence adds a valuable clarification about what the counts do not represent. Every word earns its place.

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?

This is a simple read-only tool with two required ID parameters, annotations already covering the safety profile, and an output schema available. The description adequately states what the tool returns and adds a clarifying limitation. The only gap is the lack of parameter role explanations, but the overall context is sufficient for correct invocation.

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 0%, and the tool description does nothing to explain project_id or room_id beyond their names. With 0% schema coverage, the description should compensate by clarifying parameter roles, but it does not, leaving the agent to infer the meaning and relationship of the two required IDs from context.

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 uses a specific verb ('Read') with a concrete resource (aggregate views, downloads, and link-use counts), making the tool's function immediately clear. It also distinguishes this from other analytics tools by focusing on SparkRoom usage summary metrics, which keeps it distinct from siblings like landing.get_analytics.

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: use this when you need aggregate SparkRoom usage counts rather than investor identities or diligence readiness scores. However, it does not explicitly state when to prefer this tool over alternatives or name any exclusion conditions, so the guidance is 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.