add_dashboard

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

No annotations are provided, so the description must convey behavior. It states the tool creates a dashboard, which implies a write operation. However, it does not disclose what happens to existing dashboards with the same name, whether the operation is reversible, or if it requires specific permissions. The description is minimal but not misleading.

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 sentence of 6 words, which is concise and front-loaded with the main action. However, it is arguably too brief for a tool with 5 parameters and no other documentation, sacrificing clarity for brevity.

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?

Given the presence of an output schema (which may document return values), the description can focus on behavior. However, with no annotations and 5 parameters, the description should provide more context about parameter roles and usage. It is adequate for a simple tool but incomplete for the complexity of combining worksheets with layout options.

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%, meaning the description does not explain any parameters beyond their names. The description mentions 'multiple worksheets' but does not clarify that 'worksheet_names' is a list of worksheet names, nor does it explain 'layout' options (e.g., 'vertical' vs 'horizontal'). The 'width' and 'height' parameters have defaults but no semantic context. With 5 parameters and 0% coverage, the description adds insufficient meaning.

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 dashboard combining multiple worksheets' clearly states the verb 'create' and resource 'dashboard', and the purpose of combining worksheets. It distinguishes from siblings like 'add_dashboard_action' and 'add_worksheet' by focusing on dashboard creation, but does not explicitly differentiate from 'add_calculated_field' or 'add_parameter' which have different purposes.

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?

The description provides no guidance on when to use this tool vs alternatives. It does not mention prerequisites (e.g., worksheets must already exist) or when not to use it. Siblings like 'add_dashboard_action' suggest adding actions to an existing dashboard, implying this tool is for initial creation, but this is not stated.

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