salesforce_create_note

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

Annotations already cover the readOnly/destructive/idempotent profile; the description adds context about routing through the dispatcher under JWT, tenant, and company scope. It does not describe side effects or what gets created, but it does not contradict the annotations.

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 compact, front-loaded with the action name, and organizes parameters cleanly. It earns conciseness points for no filler, though the short length contributes to under-specification in other dimensions.

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 mutating dispatcher action with optional structured inputs and an output schema, the description is too thin: it lacks what create_note does, what inputs are valid, and what outcome to expect. The routing/scope sentence is useful but does not make the tool safely invocable.

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 Args section adds minimal semantics ('free-text objective', 'optional JSON string'), but with zero schema descriptions the description must do more to explain what inputs create_note expects. It provides no structure, keys, or examples for the JSON string, leaving the agent to guess.

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 ('create_note') and its routing, so the verb and resource are clear, but it never explains what creating a note entails or how this differs from sibling Salesforce create tools beyond the name. An agent can infer the intended effect from the tool name, not from the description.

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?

No when-to-use guidance is provided; the description does not mention alternatives or conditions that should route an agent to this tool over other Salesforce create actions. It only states that it runs a domain-agent action.

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