add_marker

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It indicates the tool generates code, but does not explain the output format, side effects (e.g., does it require an existing map?), or any error conditions. This is insufficient for an agent to understand the tool's behavior fully.

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, concise and front-loaded with the main action. No extraneous information is present, and it efficiently communicates the tool's purpose.

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 absence of an output schema and annotations, the description should be more complete. It fails to explain what the tool returns (e.g., a code snippet) and lacks context about prerequisites or interactions with other tools. For a tool with 5 parameters, this is insufficient.

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 schema provides full parameter descriptions (100% coverage), so the baseline is 3. The description adds value by grouping optional features (popups, tooltips, custom icons) but does not provide additional semantic details beyond what is in the 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 the tool's purpose: generating code for adding markers to a Leaflet map, with optional features like popups, tooltips, and custom icons. It uses a specific verb ('generate code') and resource ('adding markers'), and the distinction from sibling tools like add_popup is evident.

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 its siblings. It does not mention prerequisites, limitations, or alternative use cases. For example, it does not clarify that this tool is for markers, while add_popup might be for standalone popups.

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