pmg_action_field_create

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

No annotations provided. The description labels the tool as 'MUTATION (LOW)', indicates dry-run default behavior, notes config requirements, and provides a verified API path. It discloses key behavioral traits (safety through dry-run, mutation type) beyond a simple 'create' statement.

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, starting with the purpose and mutation flag, then key behaviors, API path, and parameter explanations. Every sentence adds 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?

With 6 parameters and an output schema (not shown but available), the description covers purpose, key parameters, dry-run behavior, config requirement, and API path. It does not describe return values, but the output schema would cover that. Given the tool's complexity, this is fairly 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 input schema has low description coverage (17%), but the description adds meaning: 'name: action object name. field: mail header field to set. value: value to assign. info: optional description.' It also clarifies the confirm parameter. This compensates for the schema's lack of descriptions.

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 'MUTATION (LOW): create a field-modification action object in the PMG RuleDB.' This specifies the verb (create), resource (field-modification action), and scope (PMG RuleDB), distinguishing it from siblings like pmg_action_field_update (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 description mentions dry-run by default and confirm=True to execute, and requirement for PROXIMO_PMG_* config. It does not explicitly state when to use this tool vs alternatives like update or delete, though the context suggests creating new objects. Usage guidance is implied but not explicit.

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