Create Dashboard

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

Adds useful context beyond annotations, such as the folder path format ('FolderName/DashboardName') and the requirement that components be powered by existing reports. There is no contradiction with the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false).

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 three sentences, front-loaded with the core action, then providing usage context. Every sentence adds value without redundancy or unnecessary detail.

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 covers the primary purpose, usage context, and key prerequisites. It does not mention success responses or error conditions, but given the lack of an output schema and the presence of annotations covering safety, this is acceptable.

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 coverage is 100%, so the schema already fully describes all parameters. The description's mention of folder format and report linkage adds minimal extra meaning, as these are already captured in the schema descriptions.

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 explicitly states the tool 'Creates a Salesforce Dashboard' and enumerates component types (charts, metrics, tables, gauges), clearly distinguishing it from sibling sf_update_dashboard. The verb and resource are specific and unambiguous.

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?

Provides a clear use case ('Use when a team needs a visual summary of their metrics') and implies prerequisites (components linked to existing reports). However, it does not explicitly mention alternatives or exclusion conditions, though the clear 'create' focus differentiates from update tools.

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