salesforce_invoke_prompt_template

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

The description does not disclose side effects, permissions, or the fact that the annotations mark it as potentially destructive. It does not contradict the annotations, but it adds almost no behavioral transparency beyond 'Run' and routing information.

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 short and to the point, with no redundant fluff. The routing sentence is arguably extra context, but it does not make the description bloated.

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 description lacks context about what the prompt template does, what kind of results to expect, when to call it, and what makes it different from the many other Salesforce and invocation-related tools. It is too skeletal for an agent to use confidently.

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 description provides brief arg explanations ('Free-text objective' and 'Optional JSON string of structured inputs') which add some meaning beyond the bare schema, but they remain too vague to fully specify expected content or format for either parameter.

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 identifies a specific action ('invoke_prompt_template') and a specific domain (Salesforce), with a clear verb 'Run'. However, it relies on the tool name and generic 'domain agent action' phrasing without explaining what invoking this prompt template accomplishes, so it is not fully self-contained.

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 no guidance on when to use this tool versus any sibling tool, and no exclusions or alternative recommendations. The routing/JWT context is technical background, not usage guidance.

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