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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful operational context the annotations do not: the credit cost ('10 credits (Tier 1)'), the HTTP endpoint, and which inputs are required. It stops short of describing output shape, but an output schema exists.

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?

Front-loaded with the purpose in one sentence, followed by a compact metadata block (group, endpoint, required, cost). Nothing is padded, though the metadata lines are template boilerplate rather than prose that earns its place per-tool.

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 simple two-required-parameter calculation tool with an output schema and full annotation coverage, the description supplies enough to invoke correctly: what it computes, the system, the endpoint, required inputs, and cost. The main gap is the absence of routing guidance among the many pinnacle 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 50% — 'fields' and 'precision' are documented in the schema, while 'name' and 'date' carry only type/pattern constraints. The description restates the required set ('Required: name, date') but adds no meaning beyond that, so it does not compensate for the undocumented half. Baseline 3 for partial coverage.

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 a specific verb and resource ('Calculate four Pinnacle cycles with their age boundaries') and clarifies the meaning of the output ('life chapters of opportunity'). The 'Pythagorean system' tag plus endpoint differentiate it from the Chaldean/Kabbalistic/Vedic pinnacle siblings, though the differentiation is by label rather than explicit contrast.

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?

There is no when-to-use or when-not-to-use guidance. Given ~11 sibling pinnacle tools across systems, the description never explains why an agent would choose Pythagorean over Chaldean/Kabbalistic/Vedic, nor does it state prerequisites or prerequisites for the input date.

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