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

Annotations already declare this a safe, idempotent, non-destructive read, so the safety profile is covered. The description adds a conceptual definition of what a disposition chain is, which is useful, but it does not disclose the POST-with-body shape, that this is a computed result and not a stored resource, or anything about the cost tier beyond the bracketed metadata line.

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 prose is one efficient sentence, front-loaded with the action. The trailing bracketed metadata block (group/endpoint/cost) is structured and skimmable rather than wasteful.

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 single-purpose computed chart tool with a rich schema and an output schema, the definition is minimally adequate. It defines the concept, which is the main non-obvious piece, but omits any cue about when this is the right tool versus the sibling dignities endpoints.

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 100%, so the schema carries the parameter burden and the baseline of 3 applies. The description adds no parameter meaning beyond the one concept term ('sign rulers'), leaving mode/rulerMode semantics to the 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 states a specific verb and resource — 'Calculate planetary disposition chains' — and defines the concept inline ('the recursive sequence of sign rulers leading to the final dispositor'). This clearly distinguishes it from sibling tools like astroway_dignities_almuten (a single almuten winner) and astroway_dignities_disposition_chains_layout (a rendering of the same chains).

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 offers no when-to-use guidance, no prerequisites, and never names an alternative. An agent choosing among the many dignities siblings gets only the noun phrase to go on.

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