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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds genuinely useful non-schema context: the credit cost (10 credits, Tier 1) and the tradition grouping. It does not explain what the score represents, its range, or what inputs drive it.

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?

Two short lines plus metadata tags, front-loaded with the core purpose and free of waste. But the brevity is under-specification rather than disciplined concision: there is no second sentence earning its place because there is essentially no content beyond the name restated.

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 specialized Hellenistic technique with 15 parameters, a low schema coverage, and only four required inputs, this is far too thin. The output schema exists so return values need not be described, but the description supplies neither the meaning of the score nor any usage context, leaving the agent to guess at a niche calculation.

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% across 15 parameters, so the description is expected to compensate for undocumented fields (city, name, cosmogram, zodiacType, houseSystem, ayanamsaId). It adds no parameter meaning whatsoever, leaving the description's share of the parameter burden entirely unmet.

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 a specific astrological resource ('sect-light dignity') and the output kind ('numerical scoring'), which is more specific than the title alone. However, it never states a verb (compute/calculate) and does nothing to distinguish it from closely related siblings like astroway_hellenistic_schmidt_sect_classes or astroway_dignities_essential_dignities. An agent knows roughly what domain it hits but not precisely what it produces versus its neighbors.

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?

The only contextual cue is the bracketed group tag '[Group: Hellenistic: Hand tradition]', which categorizes but does not advise. There is no when-to-use statement, no prerequisite, and no pointer to an alternative tool. An agent must infer usage entirely from the name.

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