query_spacetrack

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

No annotations provided, so description carries the burden. It discloses authentication requirements via environment variables but does not mention rate limits, error handling, or side effects. Essential behavioral traits are partially covered.

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 relatively concise with a clear first-line purpose and structured Args. A minor point is that the env var requirement could be integrated more succinctly, but overall efficient.

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?

The description thoroughly covers parameters and constraints but lacks any mention of the output format or return value, which is critical for an agent to process results. With no output schema, this gap reduces completeness.

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 Args section explains each parameter in detail, specifying request_class values (e.g., gp, satcat), filters structure, sorting options, and pagination. This adds significant meaning beyond the schema, which lacks descriptions and enums.

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 clearly states 'Build and execute an advanced SpaceTrack query with full control' and explains that it provides direct access to the query builder with arbitrary filters, sorting, and pagination, distinguishing it from simpler retrieval tools like get_spacetrack_gp.

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 mentions required environment variables but does not explicitly guide on when to use this tool versus siblings. It implies advanced control but lacks explicit when-to-use/when-not-to-use instructions.

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