Trutine of Hermes

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds cost (250 credits) and confirmation requirement, which are useful behavioral traits beyond annotations. No contradiction.

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?

Description is compact and well-structured: technique name, group, cost warning, and example. Every piece of information adds value, and it is appropriately sized.

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 and no output schema, the description is adequate but incomplete. It lacks information about return format, behavior for invalid inputs, or edge cases. The example request body helps but does not fully compensate.

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% for 11 parameters. The description provides an example request body showing required and some optional parameters, but does not explain each parameter's meaning, format, or constraints. This is insufficient for the number of parameters.

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?

Description clearly states it applies the Trutine of Hermes technique to derive birth time from Moon's prenatal syzygy position. It uses specific verb 'derive' and identifies the resource (birth time). The tool is distinguished from the sibling 'rectification' which likely covers general rectification methods.

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?

Description includes cost warning and asks to confirm with user before invoking, which provides usage context. However, it does not explicitly state when to use this tool versus alternatives or list exclusions. Sibling 'rectification' exists but no comparison is made.

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