ephemeris_house_cusps

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

The description's 'Calculate' aligns with readOnlyHint and destructiveHint annotations. It adds credit cost and example context beyond annotations, but could mention that it doesn't modify data or return behavior more clearly.

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: a clear purpose sentence, a line for codes, credit cost, and a helpful example. No wasted words, well-structured.

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?

Despite good parameter coverage, the absence of an output schema leaves the return format unexplained. The example helps but does not fully describe what the agent can expect as output, reducing completeness.

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 coverage is 100% with parameter descriptions. The description adds value by listing resulting angles, house system codes, and an example, complementing the schema without redundancy.

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 the tool calculates house cusps and angles (ASC, MC, DSC, IC) given date, time, location, and house systems. The verb 'calculate' and the specific resource differentiate it from sibling ephemeris tools.

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?

The description provides an example and lists house system codes, aiding usage. However, it does not explicitly contrast with sibling tools or state when not to use this tool, which would be beneficial given the large sibling list.

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