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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read profile is covered. The description adds genuinely useful context beyond that: the credit cost (10 credits, Tier 1), the endpoint, and the confirmed required parameters. It does not say anything further about output behavior, but the safety bar is already met by annotations.

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 text is short, front-loaded, and structured with bracketed metadata lines, so nothing is padded or rambling. However, efficiency comes at the cost of substance: it is a stub rather than a concise description, so it only reaches the minimum-viable level.

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 values needn't be documented, but for a 15-parameter specialized Hellenistic technique the description never explains what the tool actually outputs or how it relates to the Schmidt tradition. Listing required params, cost, and endpoint is not enough for an agent to use it confidently against the many near-identical 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 only 33%, so the description is expected to compensate for undocumented parameters (city, name, cosmogram, zodiacType, houseSystem, etc.) — it does not. It merely repeats the four required parameters that the schema already marks in its `required` array, adding no semantics.

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?

"Schmidt's causation tiers" restates the title rather than describing an operation — there is no verb and no explanation of what the tool computes or returns. The only routing value is the note that it aliases `astroway_hellenistic_schmidt_levels_of_causation`, which helps identify the tool but not distinguish its function from siblings like `astroway_hels_aspectual_typology`.

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 guidance, no statement of when this technique applies, and no mention of alternatives among the many `astroway_hels_*`/`astroway_hellenistic_schmidt_*` siblings. The bracketed metadata (group, endpoint, cost) is administrative, not usage guidance.

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