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

Annotations already declare read-only, idempotent, closed-world, and non-destructive behavior, so the remaining burden is light. The description adds the useful cost tier and domain grouping, but does not disclose anything about computation requirements, authentication, or output behavior beyond what the annotations and output schema already provide.

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 operative sentence is extremely short and front-loaded, and the group/cost tags are compact. It is arguably too sparse for a complex tool, but as written it contains no wasted prose.

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 15 input parameters, low schema description coverage, and many sibling evolutionary-astrology tools, the description is under-specified. The output schema and annotations cover return shape and safety, but usage differentiation and input semantics remain missing.

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, and the description contributes no parameter-level meaning at all. It does not clarify the required date, time, latitude, longitude inputs or any optional calculation settings, leaving the agent to rely entirely on the partially documented schema.

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 names the exact deliverable: full North Node/South Node detail with rulers and conjuncts. That is specific enough to distinguish it from most evolutionary astrology siblings, which cover Pluto condition, skipped steps, or soul types, though it does not explicitly name an alternative tool.

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 [Group: Evolutionary Astrology] tag implies a broad domain, but there is no statement of when to choose this tool over sibling evolutionary tools or other chart-calculation endpoints. It also gives no prerequisites beyond the cost signal.

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