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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a small factual note that three rule sets (day/night/common) are produced, but discloses nothing about how sect is determined, what body/chart is used, or output shape. With annotations doing the heavy lifting, this is a modest 3.

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 short and front-loaded: the technique is stated in the first phrase and metadata is bracketed separately. It earns its place without padding, though brevity here costs it elsewhere.

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 natal-chart computation with an output schema, the description is far too thin. It omits inputs, sect logic, and output contents. The output schema relieves it of explaining return values, but the usage-relevant context for a chart-based tool is essentially absent.

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 says nothing about date, time, latitude, longitude, timezone, houseSystem, or the compact-mode fields/precision parameters. The one substantive behavioral element it could clarify (day vs night derived from the timestamp/location) is left entirely implicit.

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 the astrological technique (Dorothean triplicity rulers) with day/night/common variants, so the resource is identifiable. But it never says what the tool does with birth data (compute rulers for a chart), and it does not distinguish itself from close siblings like astroway_helb_triplicity_rulers or the Hellenistic dignity/rulership tools. The name carries most of the disambiguation.

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 at all. It doesn't say this returns the triplicity sect rulers for a natal chart, nor when to prefer it over astroway_dignities_essential_dignities or the Schmidt/Hand Hellenistic siblings. The only other text is group/cost metadata, which is not usage guidance.

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