create_dashboard

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

Annotations already indicate readOnly=false, destructiveHint=false, openWorldHint=true, idempotentHint=false. The description adds the WRITE_ENABLED requirement, which is useful but does not elaborate on side effects, error cases, or output behavior. Consistent with 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?

Single sentence conveying purpose and a key condition. No unnecessary words or tangents. Highly concise.

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?

While the purpose is clear, the description omits the expected return value (since no output schema), assumes understanding of 'WRITE_ENABLED', and doesn't explain prerequisites for the parameters. Could be more complete given the lack of output schema.

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 100%, so all four parameters are well-documented. The tool description does not add any parameter-specific details beyond what the schema provides. Baseline of 3 is appropriate.

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?

Clearly states 'Create a new Performance Analytics dashboard' with a specific verb and resource, and includes a prerequisite condition (WRITE_ENABLED=true). This distinguishes it from sibling tools like create_pa_indicator or update_dashboard.

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 on when to use this tool versus alternatives (e.g., update_dashboard, create_pa_breakdown). The only context is the WRITE_ENABLED prerequisite, which is a condition but not explicit usage advice.

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