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

Annotations already disclose read-only, open-world, idempotent, and non-destructive behavior. The description adds useful context by specifying 'current' and 'collected' and by naming the outputs as counts and collector status, but it does not explain what collector status includes or what the payload looks like.

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 a single, front-loaded sentence with no wasteful filler. It states the action, the resource, and the result focus in the most direct way possible.

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 parameterless, read-only overview tool with strong annotations, this description is largely complete: an agent knows what the tool returns at a high level and can invoke it without prerequisites or configuration. The only minor gap is that 'collector status' is not elaborated, but that is not critical for a no-argument status overview.

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 input schema is empty with no parameters, so there is no parameter documentation burden for the description. The baseline of 4 applies because there is nothing to explain beyond schema details, and the description does not introduce conflicting parameter expectations.

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 states a specific action ('Read'), a precise resource ('current collected aerospace source/stock counts and collector status'), and the tool's scope. This also distinguishes it from sibling aerospace data tools such as aerospace_events and aerospace_source_directory, which target different data types.

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 this tool is for checking current collection counts and collector status, but it does not explicitly state when to use it versus alternatives or mention any exclusions. There is no direct guidance about when not to use this tool or when a sibling tool would be more appropriate.

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