Greene — Lunar Myth

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

Annotations already provide idempotent and read-only hints. The description adds no behavioral context, such as what data is returned, limits, or side effects. It merely repeats the concept of lunar archetypes.

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 short (two sentences) and thus concise, but it sacrifices necessary detail. An example is given, though in an incomplete format.

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 11 parameters, no output schema, and many sibling tools, the description fails to explain what 'lunar archetypes' are, how sign and house are used, or what the output contains. The example is unhelpful.

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 0%, so the description must compensate, but it does not describe any parameters. The only clue is the mention of 'sign and house', which is not mapped to specific parameters. The example request body is incomplete and unhelpful.

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 'Lunar archetypes by sign and house' and groups it under 'Modern Psychological', which distinguishes it from other lunar tools like lunar_calendar or lunar_return. However, it does not explicitly differentiate from other Greene tools or specify exactly what 'archetypes' means.

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 explicit guidance on when to use this tool versus alternatives. The only usage hint is an example request body, which is incomplete and does not clarify context or exclusions.

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