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

With no annotations, the description must carry the full behavioral disclosure burden. It does disclose that the tool returns current information ('right now') and the output fields (names + craft), which is useful. However, it does not mention data source, update frequency, rate limits, or any failure scenarios, leaving part of the burden unmet.

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 redundant words. It earns every character by stating the resource, the temporal scope, and the output fields. This is exemplary conciseness for a simple lookup tool.

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 tool with one optional parameter, the missing explanation of 'q' is a significant gap. The output schema exists, so return structure is covered, but agents cannot fully decide whether and how to pass the parameter. The core purpose is clear, but this unresolved aspect makes the definition incomplete.

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 parameter 'q' with 0% description coverage, and the tool description does not explain it at all. An agent cannot determine whether 'q' filters by name, craft, or something else, or whether it is safe to ignore. The optional nature and default of '' suggest it may be a query string, but the description gives no hint.

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 identifies the resource (people in space) and the key output (names and craft). The phrase 'Who is in space right now' makes the operation a current-status lookup. While it lacks an explicit verb like 'list' or 'get', it is unambiguous and naturally distinct from siblings such as 'iss' or 'spaceweather'.

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 usage guidance is provided. The description does not mention when to prefer this tool over the many space-related siblings, nor does it explain any exclusions or prerequisites. An agent is left to infer the tool's role from the name alone.

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