Rectification

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

Description says 'Rectify' which implies a transformative action, but annotation declares readOnlyHint=true, creating a contradiction. No further behavioral traits beyond cost warning are disclosed.

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 front-loaded with purpose, includes group and cost warning, and provides an illustrative example. While the example adds length, it is justified. No extraneous content.

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 has complex nested input and no output schema, yet the description omits what the tool returns (e.g., rectified time, confidence). Key parameters like methods and orb are not explained. The example is incomplete, lacking these parameters.

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 17%, and the description adds no parameter explanations beyond the example. The schema provides limited descriptions for baseInput but not for other parameters like methods or orb, leaving the agent underinformed.

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 the verb 'rectify' and resource 'birth time' with method 'using life events and transit/direction hits'. However, it does not explicitly differentiate from the sibling tool 'rectification_trutine', though the mention of transit/direction hits implies a different approach.

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 a cost warning ('Heavy — confirm with user') and provides an example request body, but no explicit guidance on when to use this tool versus alternatives like rectification_trutine. Usage is implied but not formally stated.

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