addLabel

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

The description discloses the return shape: { success, data: { labelCount: integer }, message? }, which adds value beyond annotations. However, it does not explain behavioral aspects like whether labels are appended or replaced, what happens on error, or if authentication is needed. Annotations already indicate non-readonly and non-destructive, so description adds moderate context.

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 sentence that immediately states the tool's action and return value, with no wasted words. It follows the principle of front-loading the essential information.

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 complexity of the input schema (nested GeoJSON and style objects) and the presence of multiple sibling tools, the description is minimal. It provides the core purpose and return but lacks details on how labels interact with existing features or the rendering context. It is adequate but not thorough.

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 coverage is 100%, so the baseline is 3. The description does not elaborate on parameters beyond what the schema provides. For instance, it doesn't explain how the 'field' parameter is used to generate labels or how 'style' affects appearance. No additional semantic value is added.

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: 'Add property-based text labels for GeoJSON features.' The verb 'Add' and resource 'property-based text labels' are specific, and it distinguishes from sibling tools like addGeoJsonLayer or addMarker, which add layers or markers, not text labels.

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 (e.g., addGeoJsonLayer with label styling, or addMarker). There is no mention of prerequisites, context, or exclusions, making it difficult for an agent to decide without additional knowledge.

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