Stoic Elementhood

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description does add genuinely non-derivable operational facts: the POST endpoint and the '10 credits (Tier 1)' cost, which matter for budgeting. It says nothing about latency, authentication, or output shape.

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 compact and front-loads the practical facts (endpoint, required params, cost) in a scannable form. The opening sentence is short but carries almost no content, which is a wasted line rather than bloat.

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 13-parameter tool with 23% schema coverage, the description leaves the agent unable to choose this tool over its many siblings or fill the optional parameters correctly. An output schema exists so return values needn't be explained, but the absence of any interpretive or usage context is a real gap.

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 23% across 13 parameters, so the description must compensate and does not. It merely restates the four required field names with no formats, defaults, or meaning, and says nothing about the opaque optional fields such as houseSystem enum letters, cosmogram, zodiacType, or name/city.

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 names a specific doctrinal topic ('Stoic doctrine of elemental natures') within the Schmidt Hellenistic group, which does distinguish it from, say, schmidt_sect_classes or schmidt_stations_and_phases. However, it supplies no verb and no statement of what is computed or returned, so the agent knows the subject but not 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?

There is no when-to-use guidance, no exclusions, and no routing to alternatives among the many other schmidt_* tools. The '[Required: date, time, latitude, longitude]' line is an input requirement, not a usage rule.

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