Calculate a DreamRave sleep and dream chart for a birth moment.
Plan: Standard or higher · Cost: 1 credit per call.
| Name | Required | Description | Default |
|---|---|---|---|
| birth_datetime | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries full burden. It discloses that the tool is a calculation (non-destructive) and mentions credit cost and plan requirement. It does not address input validation, rate limits, or potential errors, but the cost/plan info adds some transparency.
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 only two sentences and very concise, with no wasted words. It could be better structured (e.g., using bullet points) but remains efficient and easy to parse.
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?
The tool is simple with one parameter and has an output schema, so the description does not need to explain return values. The description covers purpose, cost, and plan requirement, making it adequate for basic use. However, it lacks parameter guidance, which is a gap given the 0% schema coverage.
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%, and the description does not explain the 'birth_datetime' parameter format, expected values, or constraints. The parameter name alone is insufficient for correct invocation; the agent needs additional guidance that is missing.
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 verb 'Calculate' and the resource 'DreamRave sleep and dream chart', and it mentions 'for a birth moment', specifying the input. It distinguishes from sibling tools like 'calculate_bodygraph' by naming a different chart type, but does not explicitly contrast them.
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 implicit usage guidance by noting the required plan ('Standard or higher') and cost ('1 credit per call'), which helps an agent decide when to use it. However, it does not give explicit when-not-to-use conditions or compare with alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct type of calculation (bodygraph, composite, dreamrave, penta, transit, location search) with no overlap, making it easy for an agent to select the correct one.
Most tools follow a 'calculate_' pattern, but 'get_transit' and 'search_locations' break the pattern, introducing inconsistency. While the verbs are descriptive, the lack of uniformity may confuse agents.
With 6 tools, the server is well-scoped for a Human Design calculation API—covering all major chart types and a helper function without superfluous tools.
The tool set covers all primary Human Design calculations (individual, composite, dreamrave, penta, transit) and location lookup. Missing are tools for interpreting or persisting results, but core calculations are complete.
