Create OmniStudio Document Generation Template

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

Annotations already communicate that this is a mutation (readOnlyHint=false) and idempotent (idempotentHint=true). The description adds no further behavioral details such as whether existing templates are overwritten, deployment requirements, or side effects. It does not contradict the annotations, but it also doesn't go beyond them.

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 well-structured: an opening purpose statement followed by a clean parameter list. It is concise and front-loaded, though the parameter list partially duplicates schema descriptions, making it slightly verbose for an MCP tool.

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?

All parameters and the creation purpose are covered, but there is no output schema and the description does not mention what the tool returns or any post-creation steps (e.g., deployment). For a mutation tool with several parameters, the lack of return-value info is a notable gap.

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 provides 100% coverage with descriptions for all seven parameters, so the schema carries the heavy lifting. The description repeats each parameter with minor additions like 'unique API name' and 'the Salesforce object this template generates documents for,' but these add only marginal value 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 OmniStudio Document Generation configuration' and explains it 'links a document template to a data source for automated document creation.' This specific verb+resource combo distinguishes it from sibling tools like sf_create_dataraptor or sf_create_omniscript.

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 by explaining the purpose (automated document creation) and the object/template/data source relationship. However, it does not explicitly mention when to use this tool over alternatives or any exclusions, so it lacks the explicit 'when-not' guidance that would earn a 5.

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