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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful operational context not in the annotations: the 10-credit Tier 1 cost and the tradition grouping. It says nothing about what the technique actually produces, but with annotations carrying the behavioral burden this is adequate.

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?

Very short and front-loaded, with no filler sentences. However, the brevity comes at the cost of substance; the only content is metadata brackets and an alias note rather than a description of the operation.

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, but for a 15-parameter chart-calculation tool with no annotations about required inputs and no usage guidance, the definition leaves the agent without enough to invoke it confidently.

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?

Fifteen parameters at 33% schema coverage, and the description gives zero parameter guidance. Nothing explains how date/time/latitude/longitude interact, which required fields are mandatory for the chart, or what houseSystem/zodiacType/ayanamsa mean for a derivative-houses computation. The description does not compensate for the coverage gap at all.

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 tool name and title rather than describing what the call computes or returns. The only added information is the tradition group and the alias mapping, neither of which clarifies purpose. An agent cannot tell from this text what output to expect.

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 guidance, no prerequisites, and no differentiation from the many sibling Hellenistic/Schmidt tools (aspectual_typology, levels_of_causation, etc.). The alias note only says the two names are interchangeable, which is not usage guidance.

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