lazymac-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions geocoding and reverse geocoding but fails to describe how the tool behaves—such as input/output formats, error handling, rate limits, or authentication needs. This is inadequate for a tool with a complex parameter structure.

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 extremely concise—a single phrase that efficiently conveys the core functionality. It is front-loaded with no wasted words, making it easy to parse, though this brevity contributes to gaps in other dimensions.

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's complexity (geocoding/reverse geocoding with a nested parameter object) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral traits, parameter details, or return values, leaving significant gaps for the agent to operate effectively.

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 has 100% description coverage but only documents a generic 'params' object without specifics. The description adds no parameter semantics, failing to explain what parameters are needed (e.g., address strings, coordinates) or their formats. This leaves the agent with insufficient guidance for proper invocation.

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 tool's purpose as a 'Korean address geocoder + reverse geocoder (road / lot)', specifying both forward and reverse geocoding operations with Korean addresses. It distinguishes between road and lot address types, though it doesn't differentiate from sibling tools like 'k_address_tools' or 'ip_geolocation'.

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 provides no guidance on when to use this tool versus alternatives like 'k_address_tools' or 'ip_geolocation'. It lacks context about typical use cases, prerequisites, or exclusions, leaving the agent to infer usage from the purpose alone.

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