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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful cost/group metadata (10 credits, Tier 1, Schmidt tradition), but says nothing about computation behavior, prerequisites, or interpretation of results.

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 and front-loads the core phrase, and the alias and cost lines are compact. But it is under-specified rather than genuinely concise, spending lines on metadata while omitting functional detail.

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 described, but with a vague purpose statement, no usage guidance, and 33% parameter coverage, the description is not complete enough for an agent to confidently select and invoke this tool among hundreds of 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% across 15 parameters, and the description adds zero parameter information to compensate. For a chart calculation tool with required date/time/latitude/longitude plus many optional tuning params, this leaves the agent relying on incomplete schema documentation.

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 states the resource ('Aspect classes per Schmidt') and the tradition grouping, which does distinguish it from other Hellenistic siblings. However, 'aspect classes' is jargon that doesn't clarify what is actually computed or returned, and there is no clear verb describing the operation.

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 guidance on when to use this versus alternatives. The only routing information is that it is a cursor-friendly alias for astroway_hellenistic_schmidt_aspectual_typology, which tells the agent it is a duplicate rather than when to select it.

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