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

Annotations already declare the mutation profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false), so the bar is lower. The description adds useful behavior beyond them: exact cost (5,000 credits, Tier 7, ~50% of free monthly budget), a confirmation-before-invoking instruction, and a not-investment-advice disclaimer. That is substantial value beyond the structured fields.

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 content list is front-loaded, the bracketed metadata lines are scannable, and the cost warning is visually prominent with the emoji marker. It is telegraphic and wastes little, though the opening fragment is less self-explanatory than a full sentence would be.

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?

An output schema exists, so return-value explanation is not required. For a costly multi-param document generator the description covers purpose, required input, cost, and disclaimer, which is largely sufficient. The only real gap is routing information versus the many sibling report tools.

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?

At 60% schema coverage the schema itself already documents chart, fields, and precision in detail, so the baseline is 3. The description only restates '[Required: chart]' and adds no meaning for fields, language, precision, or whitelabel. It neither helps nor hurts relative 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 names the resource (a financial/money natal report) and enumerates the specific content it covers (2nd house, 8th house, Jupiter, Saturn), which distinguishes it from the many other reports_* siblings by topic. The verb is carried by the title rather than the description body, and 'Financial natal:' reads as a fragment, but combined with the [Group: Reports] tag an agent can identify it.

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?

It gives a clear usage directive ('Confirm with user before invoking') and flags the premium cost, which is real guidance. However it names no alternative among the crowded reports_* and financial_* family, so an agent has no help choosing this over reports_natal or financial_wealth_house. Guidance is implied rather than comparative.

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