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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful operational context not in the annotations: the tradition group and the 10-credit Tier 1 cost, which affects call budgeting. However, it never describes what "conditions analysis" computes or what the response contains.

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 prose is a single front-loaded sentence, and the group/cost/alias lines are structured metadata that scan quickly. It is not padded, though the extreme brevity borders on under-specification rather than true conciseness.

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 computationally complex tool with 15 parameters (4 required), three enums, and low schema coverage, the description is far too thin. It omits parameter usage, output shape, and any indication of what "conditions analysis" yields; the presence of an output schema excuses return-value detail but not the missing usage and parameter context.

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 and does not. It provides no explanation of the required date/time/latitude/longitude, nor of how the sidereal/ayanamsa or house-system options affect the Eros result, so it adds nothing beyond the 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?

"Eros calculation with conditions analysis" names a resource (the Lot of Eros) and adds a scope hint (conditions analysis), but it largely restates the title "Lot of Eros Detail." It does not say what a "Lot of Eros" is or how it differs from sibling Hellenistic lots such as daimon_tyche_axis or lots_of_seven, leaving the agent to infer.

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, no prerequisites beyond the required inputs, and no exclusions. The only routing help is the note that it is an alias for the longer-named Greenbaum tool, which tells the agent about the name relationship but not the use case.

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