create_soap_message_function

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds the WRITE_ENABLED requirement, informing the agent of a write operation. However, it does not elaborate on potential side effects or reversibility, but with openWorldHint already signaling side effects, the bar is lower. The description adds some value beyond annotations.

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 that conveys the purpose and a key requirement with no superfluous information. Every word earns its place, making it highly efficient.

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 moderate complexity (6 parameters, no output schema) and annotations, the description is minimally complete. It states the action and a prerequisite but does not mention return values, confirmation, or the need for an existing parent message (implied by schema). Could be improved but meets basic needs.

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?

All 6 parameters are described in the input schema (100% coverage). The tool description does not add any extra meaning or context for the parameters. Baseline score of 3 is appropriate as the schema already provides sufficient information.

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 verb 'Add' and the resource 'SOAP function (operation) to an existing SOAP Message'. It distinguishes from sibling tools like 'create_soap_message' (creates parent) and 'list_soap_message_functions' (lists existing).

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 explicitly mentions the prerequisite 'requires WRITE_ENABLED=true', giving clear context. It implies when to use (add function to existing message) and distinguishes from creating a new message, though it does not explicitly list alternatives or when-not-to-use.

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