Levels of Causation

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful operational context not in the annotations: the POST endpoint, the four required inputs, and the credit cost (10 credits, Tier 1). It still says nothing about what the response contains or how tiers are derived, but the cost/endpoint metadata is real added value.

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?

It is short and front-loaded, with no padding sentences, but the brevity is under-specification rather than economy — the one substantive line conveys almost nothing about the operation. The bracketed metadata block is useful but does not substitute for a purpose statement.

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 13-parameter tool with 23% schema coverage, this description is far too thin. An output schema exists so return values need not be explained, and annotations cover safety, but the core question — what a 'levels of causation' computation produces and when to pick it over sibling Schmidt tools — is entirely unanswered.

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 23% across 13 parameters, so the description would need to compensate and does not. It merely restates the four required fields (date, time, latitude, longitude), which the schema already marks as required, and says nothing about city, name, cosmogram, zodiacType, houseSystem, ayanamsaId, or the ayanamsa/timezone interaction.

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 is essentially the title restated: "Schmidt's causation tiers" adds no verb or resource explanation beyond the tool name. An agent cannot tell from this what the tool actually computes (a chart? a list of tiers? a classification of planets?) or how it differs from the many other Hellenistic Schmidt siblings such as sect_classes or qualities_and_quantities.

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 alternatives named, and no prerequisites stated. With dozens of Schmidt/Hellenistic siblings in the toolset, the absence of any routing hint leaves the agent to guess from the name alone.

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