mark_map_item_complete

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

Discloses key behavioral details: records under user's name, timestamp, and that it is a sign-off requiring user confirmation. With no annotations, this description compensates well by outlining implications.

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?

Three concise sentences: action, explanation of recording, and usage guidance. No unnecessary words, front-loaded with the action.

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?

Adequate for a simple one-parameter tool with an output schema. Covers purpose, usage conditions, and behavioral implications. Missing error conditions or edge cases, but not critical for this tool.

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 single parameter 'item_id' has no description in schema or description text. While the tool name implies it refers to a map item, no additional semantics or constraints are provided beyond the schema's type declaration.

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?

Clearly states it marks a map item complete and describes it as a buy-off recorded under user name and current time. The tool name itself is descriptive, and the description reinforces the purpose. It distinguishes from siblings like 'mark_map_item_accepted' by specifying 'complete'.

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?

Provides explicit when-to-use: only when user has confirmed work is done. Emphasizes user responsibility for sign-off. However, it does not explicitly contrast with alternative statuses like 'accepted' or 'rejected'.

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