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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the group (Astro-Geography) and a cost of 50 credits (Tier 3), which helps an agent budget. It does not add deeper traits such as auth needs or rate limits, so a 3 is appropriate.

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 core sentence is front-loaded and wastes no words, and the bracketed group/cost tags are compact metadata. Slightly over-terse for the number of undocumented parameters, but structurally sound.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. However, four optional/required parameters (azimuth, halfAngle, maxDistDeg) are undefined anywhere, and there is no guidance on choosing this tool over its geo siblings, leaving real gaps for a 7-parameter cost-bearing tool.

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 only 29%: only `fields` and `precision` are documented, while azimuth, latitude, longitude, halfAngle, and maxDistDeg have no descriptions. The description does not compensate, offering at most an indirect hint that latitude/longitude relate to 'a specific city' and nothing at all for azimuth, halfAngle, or maxDistDeg.

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 gives a specific verb ('Calculate') and resource ('local space influence zone lines'), plus a clarifying gloss ('lines on the map showing planet directions from that location'). This is clear enough to distinguish it from generic geo tools, but it does not explicitly contrast with the close sibling astroway_geo_local_space, leaving the agent to infer the boundary.

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 phrase 'for a chart relocated to a specific city' implies the scenario, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., astroway_geo_local_space vs astroway_geo_relocation). The agent must guess which geo tool applies to a given request.

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