addLabel

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

Description does not disclose important behavioral details such as whether the original GeoJSON is modified, whether labels are temporary or persistent, or any side effects. Annotations provide readOnlyHint and destructiveHint but description adds no extra context beyond the basic action.

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?

Extremely brief single sentence repeats the tool name. While concise, it under-specifies for a tool with 4 parameters and nested objects, lacking necessary context for correct use.

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 (nested objects, no output schema, limited annotations), the description is incomplete. It fails to explain how labels are applied, what happens to the data, or expected output, leaving significant gaps for an AI agent.

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 baseline is 3. Description adds marginal value by hinting at the field parameter ('display attribute values'), but does not elaborate on style or sessionId beyond schema definitions.

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?

Description clearly states the tool adds text labels to GeoJSON features, specifically for displaying attribute values. It effectively distinguishes from sibling tools like addGeoJsonLayer (adds the layer) and addMarker (adds point markers).

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?

No guidance on when to use this tool versus alternatives such as addMarker or other labeling methods. The description does not mention any prerequisites or contrasts with sibling tools.

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