marker_edit

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

No annotations provided; the description leaves ambiguity about behavior with invalid marker_index or whether the tool handles region start/end (only one position parameter). Does not disclose side effects or error states.

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 front-loaded with purpose and list arguments in a concise manner. Every sentence provides value without redundancy.

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?

Covers essential parameter semantics but lacks details on error handling, return value, or region-specific behavior. Adequate for a simple tool but not fully complete.

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 description adds meaning beyond the schema by explaining special values: position can be -1 to keep current, name can be None to keep. Schema only provides types and defaults.

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 states 'Edit marker/region.' with a specific verb+resource, distinguishing it from siblings like marker_add, marker_delete, and marker_get_all.

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 implies usage for editing markers/regions but provides no explicit guidance on when to use versus alternatives like marker_get_all to fetch then marker_edit, or contextual exclusions.

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