Create Global Quick Action

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

Annotations already cover the safety profile (non-read, non-destructive, idempotent, open-world). The description adds behavioral context beyond annotations by explaining placement ('accessible from the global navigation bar') and that it appears in the global quick actions menu, which is useful for understanding the scope and effect.

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 three concise sentences, front-loading the core purpose and then adding supported types and the key distinction from object-specific actions. Every sentence earns its place with 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?

The tool has 5 params but no output schema. The description explains the global action concept and supported types, while the schema covers parameter details. It falls just short of perfect completeness because it doesn't clarify conditional parameter requirements (e.g., which params apply per action type) beyond the schema's brief note on targetObject.

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 description coverage is 100%, so the schema fully documents all parameters. The description only restates the action type enum (Create, LogACall, SendEmail, Canvas) and doesn't add new semantics beyond what the schema already provides for naming conventions or conditional parameter usage.

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 a global quick action, specifies where it appears (global navigation bar), and explicitly distinguishes it from object-specific actions via 'Global actions are not tied to a specific object.' This differentiates it from the sibling tool sf_create_quick_action.

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 implies when to use this tool by emphasizing 'global' and 'not tied to a specific object,' which contrasts with object-level quick actions. However, it does not explicitly name an alternative tool or state 'use sf_create_quick_action for object-specific actions,' so it stops short of full explicit guidance.

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