get_dashboard_summary

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds genuinely non-obvious behavior: counts and recent items stay scoped to the caller even for admins, and storage is reported twice (per-user against quota, installation-wide against the system cap). It does not mention cost, caching, or rate limits, but for a zero-argument read this is solid added 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?

Three sentences, each doing distinct work: first enumerates the payload, second clarifies scoping and the dual storage report, third routes to the alternative. Front-loaded with the return contents and free of filler.

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?

With no parameters and no output schema, the description must carry the return-value burden, and it does so by naming every section of the response including the quota-vs-cap distinction. Nothing an agent needs in order to call or interpret this tool is missing.

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 tool takes no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It does not need to explain argument semantics at all.

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?

States a specific verb and resource ("Get the calling user's dashboard") and then enumerates exactly what it contains: counts of datasets/models/experiments, five most recent datasets and experiments, storage usage, and latest analysis from the most recent completed/running experiment. An agent can distinguish it from list_datasets, list_experiments, and get_system_stats without opening any schema.

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?

Explicitly routes system-wide needs to get_system_stats and notes it is admin only, which is a clear alternative-plus-condition. It does not, however, say when to prefer the dashboard summary over the sibling list_* tools for per-user enumeration, so one comparison is left implicit.

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