Create Quick Action

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

The description adds minimal behavioral context beyond the annotations. It mentions 'via the Metadata API' which hints at deployment, but does not disclose side effects, permission requirements, or return behavior. Annotations already indicate mutation and idempotency, so the description does not contradict but adds little extra value.

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: three sentences, front-loaded with purpose, and no wasted words. It efficiently covers purpose, supported types, and optional parameters.

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?

For a create tool with 7 parameters and no output schema, the description covers the essential purpose, supported types, and optional parameters. Annotations cover safety traits. It does not mention return values or error conditions, but that is not critical with no schema present. The description is adequate overall.

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 100%, so the schema fully documents all parameters. The description adds a small hint that targetObject is for Create type and fields are for the layout, but the schema already states these (e.g., targetObject is 'required for Create type'). Thus the description provides little beyond 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 clearly states the tool creates an object-specific quick action via the Metadata API and lists the supported action types. This distinguishes it from the sibling sf_create_global_action, making the purpose unambiguous.

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 provides clear context: it is for object-specific quick actions and supports specific action types (Create, Update, LogACall, SendEmail). While it doesn't explicitly name alternatives like sf_create_global_action, the 'object-specific' qualifier implies when to use this tool versus global actions, and the type list implies limitations.

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