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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful operational context not in the annotations: the POST endpoint and the cost (10 credits, Tier 1), which is important for a paid API. It still says nothing about what the computation is sensitive to or how the response is shaped.

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-loaded with the purpose sentence, which is good. However, the bracketed metadata block is largely boilerplate, and the [Required: ...] line duplicates the schema's required array rather than earning its place.

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 15-parameter computed-chart tool, the definition is thin: it never explains what sect classifications mean, which optional inputs change the result, or how this endpoint relates to its Schmidt/Hellenistic siblings. The existence of an output schema excuses it from describing return values, but the input-side and selection-side gaps remain significant.

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 must compensate for undocumented options like houseSystem, zodiacType, and ayanamsa that plausibly affect the classification. Instead it only restates the four required parameters, which the schema already marks as required, adding no semantics beyond it.

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?

"Sect classifications per Schmidt" identifies the resource and the tradition, but it is a noun phrase with no verb and no explanation of what a sect classification actually is (day/night sect, planet placement in sect, etc.). It does not distinguish itself from nearby siblings such as astroway_hellenistic_hand_sect_strength or the other Schmidt-tradition tools, so the agent must guess which sect-related endpoint is wanted.

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 description gives no when-to-use guidance, no prerequisites, and no alternatives. The bracketed [Group]/[Endpoint]/[Required] lines are routing metadata, not selection criteria, so an agent cannot tell from this text when to call this instead of hand_sect_strength or any other Schmidt tool.

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