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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the HTTP endpoint, the four required inputs, and the cost (10 credits, Tier 1). It discloses nothing about what the computation returns or any limits, but the cost and required-input callout exceed what annotations provide.

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 layout is compact, front-loaded and easy to scan, with no prose padding. It is slightly redundant in restating the required-parameter list that the schema already declares, but overall it wastes little space.

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 spelled out, but for a technique-specific Hellenistic computation sitting among hundreds of siblings the description leaves the agent without any sense of what the result represents or when it applies. Combined with 33% schema coverage, the definition is too thin to be complete.

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 — instead it merely repeats the four required fields already declared in the schema's required array. No meaning is added for the many undocumented parameters (houseSystem, zodiacType, cosmogram, etc.), leaving the agent to infer their effect.

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?

"Derived-house technique" essentially restates the title "Derivative Houses" without saying what the tool computes, what a derived house is, or what output the agent gets. The endpoint and group tags identify the family but add no functional verb+resource description. An agent cannot tell from this text what this call actually produces.

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 exclusions, and no comparison to alternatives. The only routing hint is the parenthetical that this is a "Cursor-friendly alias" for astroway_hellenistic_schmidt_derivative_houses_method, which does tell the agent it is a duplicate name — useful, but it is one hint, not usage guidance across the vast Hellenistic/Schmidt sibling set.

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