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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description's only additional context is the billing line '[Cost: 10 credits (Tier 1)]', which is genuinely useful operational information absent from the annotations. It says nothing, however, about what a 'sect classification' actually consists of or whether a day/night chart is required.

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 three lines are compact and front-loaded with no filler, so nothing needs trimming. The problem is the opposite of verbosity: it is undersized for a 15-parameter astronomical computation, leaving the structure adequate but hollow.

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 need not be described, and annotations cover safety. But for a Schmidt-tradition computation with 15 parameters and a large set of near-identical siblings, the description supplies no domain definition, no usage context, and no parameter help — an agent could not confidently choose it or call it correctly from this text alone.

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?

With 15 parameters and only ~33% schema description coverage, the description carries a compensation burden it does not meet — it mentions no parameter at all. Even the well-documented astrological controls (ayanamsa vs. ayanamsaId, timezone vs. timezoneOffset, fields, precision) get no elaboration, and the four required birth-data params are the only ones an agent can infer unaided.

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: 'Sect classifications per Schmidt' adds only the author attribution, which the tool name (schmidt_sect_classes) already conveys. It names no verb and no scope, so an agent cannot distinguish it from the many adjacent Schmidt/Hellenistic siblings (asterisk: astroway_hellenistic_hand_sect_strength, the hels_* cluster) 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?

No when-to-use, when-not-to-use, or alternative-tool guidance is present. The '[Group: Hellenistic: Schmidt tradition]' tag implies a tradition context but does not tell the agent when this computation is the right choice versus sect-strength or the parallel Brennan/Greenbaum variants.

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