ipt_replace_eml

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses that the operation writes/replaces, but it does not warn that existing metadata will be overwritten, nor does it explain the confirm gate or validation behavior.

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 one concise sentence with no redundant filler. The bracketed '[writes to the IPT]' hint adds a useful side-effect signal without bloating the text.

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?

Without annotations or an output schema, a destructive metadata-replacement tool needs more context about overwrite consequences, required confirmation, and validation effects. The description and schema leave these gaps to the 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 50%, so the description needs to help with undocumented parameters. It adds 'local path' meaning to path, but it does not clarify validate or confirm beyond the schema's existing confirm description. Partial compensation only.

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 identifies the action ('Replace'), the resource ('resource's metadata'), and the input source ('an EML file from a local path'). This distinguishes it from siblings like ipt_get_draft_eml or ipt_set_metadata_fields.

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 operation is understandable, but there is no explicit guidance about when to use this tool versus alternatives such as ipt_set_metadata_fields or ipt_validate_resource. The usage context is implied by the verb and resource rather than stated.

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