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

No annotations are provided, so the description must carry the behavioral burden. It discloses the null behavior (none within ~50 km) and specifies straight-line distance, which is useful. However, it does not state whether the tool is read-only, any error conditions, or the structure of the result, though an output schema exists. Given the minimal nature, a 3 is appropriate.

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 a single, efficient sentence that front-loads the core purpose and includes the critical null and distance caveat. It avoids extraneous detail and is appropriately sized for a simple query tool.

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 tool has an output schema, the return structure is covered. However, the description does not explicitly state that the tool takes a suburb_name parameter, which is a key missing link for an agent to call it correctly. The 50 km cutoff is disclosed, but the absence of any mention of the input requirement makes the definition incomplete for a single-parameter tool.

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 sole parameter, suburb_name, has 0% schema description coverage. The description implies the tool operates on a suburb but never explicitly names the parameter or explains its format (e.g., exact name, case sensitivity). The agent must infer that suburb_name refers to the suburb being queried. This is a gap in meaning beyond the bare schema.

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 what the tool returns: the nearest beach and hospital with straight-line distances, including a null case. It differentiates from other suburbs_lifestyle_* tools by naming specific amenities (beach and hospital), so an agent can distinguish it from, say, suburbs_lifestyle_cbd or suburbs_lifestyle_livability.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention any preconditions, alternatives, or exclusions. The description simply states what it does without contextualizing it among the many sibling tools, leaving the agent to infer applicability.

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