Antiscia

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. Description adds 'calculate' confirming read-only operation but does not disclose other behavioral traits like required input relationships (e.g., chart vs. transit) or output format.

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 description is short and includes an example request, but the group/cost metadata line adds noise. Front-loaded with the main action, but the example could be integrated more concisely.

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?

With 11 parameters, no output schema, and a technical astrological concept, the description is insufficient. It omits how 'natal planets' are determined, how aspects are returned, and what the result represents.

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?

Input schema has 11 parameters with 0% description coverage, and the description does not explain any parameter beyond an example request body. The agent receives no semantic guidance for the many optional 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?

Description states 'Calculate antiscia and contra-antiscia, plus aspects to natal planets' with specific verb and resource. However, the term 'natal planets' is ambiguous given the single-chart input, and the tool is not differentiated from siblings like hellenistic_greenbaum_antiscia_hellenistic.

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 guidance on when to use this tool versus alternatives. The description lacks context for selecting this tool over related antiscia tools among the extensive sibling list.

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