geo_add_reverse

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. The verb 'Add' minimally implies a mutating operation, but the description reveals nothing about side effects, what files or configuration get modified in the directory, whether the api_key triggers external provider calls, reversibility, or failure modes. This is a significant gap for a tool that likely writes configuration or code.

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?

At three words, the description is under-specified rather than concise. There is no structure, no front-loading of critical constraints, and no explanatory payoff — the single sentence simply restates the name. This is a case of brevity depriving the agent of needed information, not efficient prose.

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?

Despite low complexity (2 params, no output schema, no nested objects), the definition is completely inadequate. An agent cannot infer which geocoding provider or service this targets, what the api_key is for, what happens inside the directory, or whether prior setup is required. With no annotations and 50% schema coverage, the description needed to carry the full context and delivers almost none of it.

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 50%, and the description adds zero meaning for either parameter. The api_key parameter is undocumented in both the schema (just 'string') and the description, leaving an agent unable to determine which geocoding provider it authenticates, whether it is effectively required, or how it is consumed. The directory parameter receives no contextual enrichment beyond the schema's 'Project directory'.

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 'Add reverse geocoding' is essentially a word-for-word expansion of the tool name geo_add_reverse, filling in the implied noun. It states a verb and a domain concept but gives no operational detail about what 'adding reverse geocoding' actually entails — no target system, no effect, no deliverable. It neither distinguishes itself from siblings like geo_setup_provider or geo_add_batch nor explains the geocoding workflow context.

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 whatsoever on when to use this tool versus alternatives. Nothing indicates whether geo_setup_provider must run first, whether this complements geo_add_batch, or whether an api_key prerequisite exists (despite the api_key parameter). There are no exclusions, alternatives, or context cues beyond the weak implication carried by the geo_* name pattern.

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