getBrandDashboard

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds minimal behavioral context. It does not disclose what data the dashboard includes, how it is aggregated, or any limitations. A score of 2 reflects that the description does not add value beyond 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?

The description is a single sentence, which is concise. However, it is minimal and does not fully leverage the space to add useful context. It is not overly verbose but also not optimally informative for an agent.

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 that there is no output schema and the tool is simple (no params), the description should still clarify what the dashboard shows. It does not describe return values or the structure of the dashboard, leaving the agent uninformed about what to expect from the response.

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 input schema has zero parameters, so the description naturally adds no parameter meaning. With 100% schema coverage and no params, the baseline is 4. The description does not need to explain 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 clearly states 'Get your brand's overall performance dashboard', which is a specific verb ('Get') and a resource ('brand's overall performance dashboard'). It distinguishes itself from siblings like getCampaignPerformance and getEarningsSummary by referring to the overall brand dashboard. However, 'overall performance dashboard' is somewhat generic, reducing clarity slightly.

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 usage guidelines are provided. There is no indication of when to use this tool versus alternatives like getCampaignPerformance or getEarningsSummary. The description lacks any context cues for appropriate use.

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