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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The one real addition is the billing trait — [Cost: 10 credits (Tier 1)] — which is not in the schema or annotations and matters to an agent deciding whether to call it. Nothing else behavioral (error modes, limits) is disclosed.

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 bracketed metadata block is scannable and front-loads the concept line, but much of it is scaffolding (endpoint path, required-params list) that duplicates structured data already available to the agent. The alias sentence earns its place; the endpoint and required lists do not.

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 explained, and the annotations cover safety. However, for a doctrinally obscure tool with 15 parameters at 33% coverage, the description gives no sense of what the result represents or which optional parameters matter (e.g. ayanamsa/zodiacType shift the whole computation), leaving the agent under-equipped relative to the tool's complexity.

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 coverage is only 33%, so the description should compensate for the 11 undocumented parameters, but it does not. The [Required: date, time, latitude, longitude] line merely restates what the schema's `required` array already says, adding zero meaning for city, name, cosmogram, zodiacType, houseSystem, or the compact-mode fields.

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?

"Stoic doctrine of elemental natures" names the subject area and the [Group: Hellenistic: Schmidt tradition] tag places it among the schmidt_* siblings, so it is not a pure tautology. But it never says what operation is performed or what the tool returns — a chart computation, a doctrinal text, or a classification — so an agent cannot tell what calling it actually yields.

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 note that this is a cursor-friendly alias for `astroway_hellenistic_schmidt_stoic_elementhood` is genuinely useful routing information: it tells the agent this is the same capability under a short name and shouldn't be called alongside the canonical one. Beyond that there is no when-to-use/when-not guidance versus the other Schmidt or Hellenistic tools.

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