astrology_get_coordinates

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

The description adds information beyond annotations (readOnlyHint, idempotentHint) by specifying the geocoding service (OpenStreetMap). It does not contradict annotations. A score of 4 reflects that while annotations already indicate safety, the description provides useful context about the external dependency.

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 two sentences with no wasted words. The first sentence states the core action, and the second provides the use case. It is front-loaded and gets straight to the point.

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 the simplicity of this tool (1 parameter, no output schema), the description adequately covers what it does and why it is used. However, it could be slightly more explicit about the return format (e.g., 'returns latitude and longitude as numbers'). Still, the agent can infer from the name and use case.

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?

The input schema already provides 100% description coverage for the single parameter 'location', including the format 'City, Country'. The description restates the conversion purpose but does not add significant new parameter semantics beyond the schema. Baseline 3 is appropriate.

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 ('Convert'), resource ('location string'), and output ('geographic coordinates'). It also mentions the specific service (OpenStreetMap geocoding) and distinguishes from the sibling tool 'astrology_calculate_natal_chart' by describing the prerequisite use case.

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 explains when to use this tool ('before calculating a natal chart when only the city name is known'), which provides clear context. However, it does not explicitly state when not to use it or mention alternatives, though the sibling tool is the only alternative.

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