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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description's one genuine addition is the cost disclosure (50 credits, Tier 3), which is useful for an agent deciding whether to spend budget, but it says nothing about latency, accuracy, or result determinism beyond the idempotent annotation.

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?

Front-loaded with the core action and tightly structured; the bracketed group/endpoint/required/cost lines are compact and scannable. The [Required] line is redundant with the schema's required array, costing a little density.

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 15-parameter geo tool sitting among many overlapping siblings (ACG, zenith, relocation, local-space influence zone), the description gives no routing guidance and no domain context on when a local space chart is the right output. The existing output schema excuses it from explaining return values, but the selection and parameter gaps leave it under-specified.

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 description coverage is only 33% across 15 parameters, so the description carries a compensation burden it does not meet. It merely restates the four required parameters already declared in the schema and adds no meaning for the optional ayanamsa, houseSystem, zodiacType, cosmogram, or precision parameters.

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?

States a specific verb ('Calculate') and resource ('local space chart') and even defines the output conceptually (azimuth and altitude of each planet from a geographic location at the birth moment), which implicitly separates it from geo_acg or geo_zenith. However, it never names or contrasts any sibling, so the agent must infer the distinction from domain knowledge.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as astroway_geo_local_space_influence_zone or astroway_geo_relocation, which share the same geo-astrology space. The bracketed metadata lists required inputs and cost but nothing about selection context.

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