salesforce_pipeline_report

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

No annotations are present, and the description fails to disclose any behavioral traits such as read-only vs. destructive, idempotency, rate limits, or what side effects occur. The routing info is generic and adds no behavioral context.

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 brief (two sentences plus an Args line) but lacks essential content. The first sentence restates the tool name without adding clarity. It could be more concise if it focused on functional description rather than routing details.

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 omits what the tool returns (despite context indicating an output schema exists), how it behaves, and the semantics of the pipeline report. For a simple tool with one parameter, it should at least clarify the purpose and output.

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 single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation', but the description does not specify expected keys or structure. With 0% schema description coverage, this minimal addition does not sufficiently compensate for the lack of parameter documentation.

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 vaguely states it's a Salesforce connector operation for pipeline_report, but does not specify what the tool actually does (e.g., retrieve, generate, list). The name implies a report, but no verb or outcome is given. Sibling Salesforce tools like salesforce_bulk_* have more descriptive purposes, making this one ambiguous.

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 guidance is provided on when to use this tool versus other Salesforce tools or alternatives. There is no mention of prerequisites, typical use cases, or conditions where this tool should or should not be used.

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