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 states the tool returns live lat/lon but does not disclose behavior such as whether it requires a query parameter, what happens with an empty query, rate limits, or whether it returns additional data like altitude or timestamp. The behavior is minimally transparent but lacks important operational details.

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 extremely short, which is concise, but it is under-specified rather than efficiently informative. It front-loads the core purpose but omits necessary context. It is not bloated, but it does not earn its place as a complete tool description.

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?

Given the tool's simplicity, the description is nearly adequate, but the lack of parameter explanation and behavioral details makes it incomplete. The output schema exists, so return values are partially covered, but the input semantics and usage context are missing. An agent could call it, but not with confidence about the 'q' parameter.

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 schema has one optional parameter 'q' with a default of empty string, and schema description coverage is 0%. The description does not explain what 'q' means or how it affects the result. Since the tool is about ISS position, 'q' might be a query or location, but the description provides no clarification, leaving the agent to guess.

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 the tool's purpose: 'ISS Position: Live International Space Station lat/lon'. It identifies the resource (ISS) and the output (lat/lon), but it is terse and doesn't distinguish it from sibling tools like 'spacepeople' or 'spaceweather' or 'whatsnearby' that might also relate to space or location. It is clear enough for a simple lookup but lacks differentiation.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions. An agent would have to infer that this is for current ISS coordinates, but there is no explicit routing or comparison to siblings.

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