pls_update_map

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

The description adds value beyond annotations by requiring a confirmation parameter and specifying the return format. It aligns with the destructiveHint annotation, indicating a write operation, without contradiction.

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 concise with bullet points, emojis, and clear sections. Every sentence is informative and there is no 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?

Given the absence of an output schema, the description provides the return format. It covers the confirmation requirement and hints at field selection. It is adequate for an update tool with well-defined siblings.

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 covers all parameters with descriptions (100% coverage). The description adds a useful hint about only passing fields to change, which complements 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 '更新地图实体' (update map entity) clearly states the action and resource. It distinguishes from sibling tools like pls_create_map and pls_delete_map by specifying 'update'.

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 hint '确认+只传需改字段' (confirm + only pass fields to change) provides clear guidance on how to use the tool. However, it does not explicitly state when to use this tool versus alternatives, but the context makes it obvious.

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