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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's genuinely additive facts are the credit cost (10 credits, Tier 1) and the HTTP endpoint, which help an agent judge expense. It says nothing about sect handling, computational prerequisites, or whether ayanamsa/zodiacType materially change the result.

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 definition is short, front-loaded with the purpose line, and the bracketed metadata lines are scannable rather than prose padding. Slightly over-reliant on a structured block instead of explanatory sentences, but nothing is wasted.

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 computation with an output schema present (so return values need no explanation), the description is still too thin: it never explains what the Daimon/Tyche axis is used for astrologically, how it relates to the duplicative sibling, or which of the many optional parameters actually matter. An agent has the mechanics but not the judgment needed to invoke it well.

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 real burden — yet it only restates the four required fields already declared in the schema's required array. The eleven optional parameters (city, name, cosmogram, zodiacType, houseSystem, ayanamsaId, etc.) receive no clarification, and the sidereal/tropical distinction is especially relevant for a Hellenistic tool and goes unmentioned.

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?

"Spirit-Fortune axis as primary chart spine" names a recognizable astrological construct, so the resource is identifiable, but there is no verb describing what is produced (compute? list? interpret?) and no indication of what the axis output means for the agent. It also fails to distinguish itself from the near-identical sibling astroway_helg_daimon_tyche_axis, which carries the same title-ish concept under a different prefix.

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 bracketed block states required inputs and cost but gives no when-to-use guidance, no prerequisites, and no routing advice relative to the many other Hellenistic lot/spine tools in the sibling list. An agent cannot tell from this text why it would pick this over astroway_helg_daimon_tyche_axis or the Greenbaum lots tool.

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