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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description usefully adds the cost (10 credits, Tier 1), the endpoint, and the required inputs, which are not in the annotations. It says nothing about response shape or how the ruler assignment is bounded, but with annotations and an output schema in place the added cost/endpoint context earns a mid score.

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?

Extremely tight: one subject line followed by bracketed metadata, with the technique name front-loaded. Nothing is padded, though the metadata block substitutes for content rather than supplementing it.

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 chart-computation endpoint this is thin. The output schema relieves it of describing return values, but it leaves unaddressed which optional inputs matter (sidereal school, zodiac type, house system) and give no indication of when the bounds technique is applicable — a gap that matters in a catalogue with hundreds of near-identical Hellenistic siblings.

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 is expected to compensate and does not. It merely restates the four required fields already encoded in the schema's required array and explains none of the optional parameters (ayanamsa, zodiacType, houseSystem, fields, precision, timezone) or how they alter the bound-ruler output.

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?

Names a specific astrological technique (Ptolemaic Egyptian bounds rulers) and the group tag places it in the Hand tradition rather than the Greenbaum/Schmidt/Brennan branches. However, it never states the verb or what is actually returned — no indication that it computes/returns the bound (term) ruler per zodiacal segment for a chart. It also does not distinguish itself from close siblings like astroway_hellenistic_hand_decanic_rulers, whose name suggests a similar ruler-table output.

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 description gives no when-to-use guidance, no prerequisites, and no alternatives. The only contextual lines are the endpoint, required-field list, and credit cost, which are operational metadata rather than usage guidance. An agent must infer from the technique name alone whether bounds are the right tool versus decans, critical degrees, or lots.

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