Transit Midpoints

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no behavioral traits beyond these, so it does not contradict but also does not add value. A score of 3 is appropriate since the annotations handle the safety profile adequately.

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 very concise at two lines plus an example, which is efficient but sacrifices completeness. Every sentence earns its place, but the example is vague and does not clarify parameter usage. It is appropriately front-loaded with the purpose and group.

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?

Given the high complexity (16 parameters, no output schema), the description is severely incomplete. It omits explanations for essential parameters like timezoneOffset, latitude, longitude, zodiacType, ayanamsaId, cosmogram, targetTime, converse, withTnp, etc. The agent cannot determine how to correctly set these parameters from the description alone.

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?

With 16 parameters and 0% schema description coverage, the description should compensate but fails to do so. The example only shows placeholders 'chart' and 'targetDate' without explaining any specific properties. No parameter semantics are provided beyond what is in the raw schema.

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 clearly states it computes transits hitting natal midpoints in a 90° dial, specifying the verb 'hitting' and the resources 'transits' and 'natal midpoints'. It distinguishes from general transit or midpoint tools by mentioning the 90° dial and the Cosmobiology group. However, it does not explicitly differentiate from other cosmobiology tools like 'cosmobiology_midpoint_pictures' or 'transits'.

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 guidance on when to use this tool versus alternatives. The description only mentions the Cosmobiology/Hamburg School group for context but does not state when-not-to-use or suggest sibling tools. The example request body is too vague to provide usage direction.

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