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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the output is a lat/lon/timezone tuple that other tools require, establishing it as a prerequisite step. It stops short of describing match ambiguity or failure modes, deferring those to an external docs URL.

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?

Labeled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH) make it scannable and front-loaded, and it avoids prose padding. The INPUT CONTRACT does duplicate schema details already stated in the parameters, a minor redundancy.

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?

With an output schema present, annotations covering safety, and all params documented, the description only needed to add positioning and workflow. It does exactly that, so an agent has everything required to call it correctly and chain its output.

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 100%, so the schema already documents all four parameters including defaults, range and enum. The INPUT CONTRACT section restates query length, limit bounds and the country code without adding syntax or format guidance beyond the schema, so baseline 3 applies.

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?

Opens with a specific verb and resource: turns a place name into latitude, longitude and IANA timezone. It also states the output's role for downstream tools, which no sibling can claim, and explicitly notes it is the only place-lookup tool in the set.

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 WORKFLOW block gives explicit BEFORE (none) and AFTER (named consumers such as asterwise_get_natal_chart, asterwise_get_panchanga, asterwise_get_muhurta) plus a DO NOT CONFUSE WITH line. An agent knows exactly when to call this and what to do with the result.

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