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

No annotations are provided, so the description carries the full burden. It usefully discloses a genuine prerequisite — a tracker licence token — which an agent cannot learn from the schema, but says nothing about whether zero-count groups are returned, pagination, or output shape.

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 sentences, zero waste, with the operation and grouping options front-loaded and the licence prerequisite trailing. Nothing to trim.

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 one-parameter aggregate with no output schema and no annotations, the definition covers what the tool does and its auth requirement. It leaves open the return structure and grouping edge cases, which matters somewhat since no output schema exists to document them.

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%, but the single parameter is a self-documenting enum of theatre/layer/awardee, and the description echoes those values. It adds no meaning beyond the schema — no guidance on which dimension to pick for which question.

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 — counts of tracker award lines — plus the grouping dimensions, which separates it from the raw listing sibling tracker_awards. It never names that sibling explicitly, so the differentiation is inferable rather than stated.

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 word 'counts ... grouped by' implies this is the aggregation path rather than the row-listing path, but no alternative (tracker_awards, compare_companies, tracker_vendor_matrix) is named and no when-not condition is given. Usage is left to inference from the phrasing.

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