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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, covering the safety profile. The description adds useful context beyond that: the '(API Pro)' tag signals an access requirement, and it names the returned payload (angles, planets with orbs, life-sphere scores), but it does not discuss rate limits, error handling, or the time-null withholding behavior documented in the schema.

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 a parenthetical tier note; every element contributes and there is no filler. It is perhaps overly terse for a tool with nested parameters, but it is structurally clean and free of redundancy.

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 two nested required parameters, no output schema, and only 0% top-level schema description coverage, the description is too thin. It helpfully enumerates the returned contents, but it omits input format expectations and the important behavior around unknown birth time, which the schema alone must carry.

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?

Top-level schema description coverage is 0%, and the description does not explain the two required objects (birth and location) or their required fields. It only vaguely maps to the two inputs via 'one place against one chart', leaving the agent to read the nested schema for all meaningful parameter detail.

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 and output: astrocartography for one place against one chart, returning relocated angles, planets with orbs, and life-sphere scores. It implicitly distinguishes itself from multi-place siblings like best_cities by saying 'one place', but lacks an explicit action verb such as 'computes' or 'scores' to remove all ambiguity.

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?

There is no explicit guidance on when to use this tool versus alternatives. The phrase 'One place against one chart' hints at a single-location use case compared to a multi-location tool, but no sibling is named and no conditions or exclusions are stated.

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