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

goes well beyond the readOnly/destructive annotations: it discloses the pattern payload (tightness score 0-100, dissociassociate flag, one-line interpretation) and, more valuably, the built-in suppression algorithm — a Grande Cross suppresses its contained T-squares and a Kite suppresses its underlying Grande Trine. An agent otherwise could not predict that some patterns are intentionally omitted from the output. Remaining undisceclosed: behavior when no patterns exist and output ordering.

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 payload and disambiguation information is information-conceptually dense and frontLoaded — the verb+resource is first. However, the enumptions of pattern names duplicates the title, and the closing list of 'useful for' use-cases reinforces the usage guideline at the cost of a little redundancy, making it slightly longer than necessary.

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 10-parameter tool with no output schema, the description lists the data each pattern carries but never specifies the response shape — whether the result is a top-level array, an object keyed by pattern type, or how an empty chord (no patterns found) is represented. Required parameters are birth-data only and are fully schema-described, so the call can be made correctly; the ambiguity is in the return contract and edge cases.

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% — every parameter has a detailed description, defaults, enums, and a concrete example (the schema's nodeType explanation about true vs. mean is exceptionally complete). The description itself adds nothing about parameters, so the baseline 3 applies: the schema carries the full burden.

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 first sentence states a specific verb ('Identify') and a specific scope ('multi-plant configurations in a birth chart'), then enumerates all seven pattern types it handles. This clearly separates it from sibling tools like post_astrology_aspects (pairwise?) and post_astrology_natal_chart, which the tool list shows as separate resources — an agent can pick this tool without opening the schema.

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 final sentence names concrete use cases ('personalized atal report engines' 'astrology chatbots' chart pattern callouts'), giving clear when-to-use context. However, it does not explicitly name sibling alternatives it competes with (e.g., post_astrology_aspects for pairwise aspects, post_astrology_natal_chart for the full chart) or state when NOT to use this tool.

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