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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states only that it creates an opportunity, but fails to mention persistence, required fields, permissions, error behavior, or any side effects, offering no insight beyond the tool name.

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 a single short sentence, but it adds no value beyond the name. This is under-specification rather than effective conciseness, as every word merely restates what is already obvious from the tool name.

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?

With no annotations, no output schema, and zero parameter documentation, this description is woefully incomplete. It fails to provide essential context for a mutation tool with four parameters, making correct invocation nearly impossible.

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 0%, yet the description provides no parameter details. It does not explain what oppName, stage, amount, or closeDate are, their formats, required status, or how they map to Salesforce fields, leaving the agent unable to correctly construct parameters.

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 'Create a new Salesforce opportunity' is a near-verbatim expansion of the tool name, providing no new or clarifying information. It does not distinguish the tool from siblings beyond what the name already implies, making it essentially a tautology.

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?

There is no guidance on when to use this tool versus alternatives. No mention of Salesforce prerequisites, or when to prefer this over other create tools like sf_create_contact or hubspot_create_deal, leaving the agent without decision-relevant context.

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