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

With no annotations, the description carries the full behavioral burden. It usefully discloses the dataset scope ('67 checked counter-UAS award lines') and the licence-token requirement, but it does not describe return format, pagination, or other operational behavior beyond what 'Query' implies.

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?

Three short sentences, front-loaded with the resource and scope, followed by filters and prerequisite. Every sentence earns its place with no waste.

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 simple read/query tool with fully described optional parameters, the description covers purpose, scope, filters, and authentication. The main remaining gap is that no output schema exists and the description does not hint at the return shape or default behavior when no filters are supplied.

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 coverage is 100%, so the schema already documents all three parameters with examples. The description restates the filters and adds the term 'kill-chain layer' for the 'layer' parameter, but it does not add material syntax or behavior beyond the schema.

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 ('Query') and resource ('67 checked counter-UAS award lines'), making the tool's purpose clear. It does not explicitly differentiate itself from siblings such as tracker_aggregate or tracker_vendor_matrix, so it falls short of 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?

It states that the tool can filter by theatre, kill-chain layer, or awardee substring and that a tracker licence token is required, which gives implied usage context. However, it does not say when to use this tool versus alternatives like tracker_aggregate or tracker_schema, and it provides no exclusions.

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