get_dashboard_extract_info

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

No annotations are provided, so the description carries the full burden. It states the tool returns refresh times but does not disclose whether it is read-only, requires permissions, or has side effects. The description lacks behavioral context beyond the return value.

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 relatively concise (two sentences plus Args/Returns). It is front-loaded with the purpose. However, the Args/Returns syntax repeats information and could be streamlined.

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 low complexity (1 simple parameter) and the existence of an output schema, the description is adequate but not complete. It lacks usage context, alternative tool mentions, and behavioral details. The output is vaguely described as 'Workbook info with all datasource extract refresh times'.

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 0%, but the description adds meaningful details: it explains the parameter 'workbook_name' with a description ('Name of the workbook/dashboard') and provides an example ('Daily Sales Metrics'). This adds clarity beyond the schema's bare string type.

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 it retrieves extract refresh information for all datasources in a dashboard/workbook. It uses specific verbs ('Get extract refresh information', 'Shows when each underlying datasource was last refreshed') and resource ('dashboard/workbook'). While it distinguishes from siblings implicitly (e.g., get_datasource_extract_info is for a single datasource), it does not explicitly differentiate.

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 an Args section with an example value but does not specify when to use this tool versus alternatives like get_datasource_extract_info or find_stale_extracts. No guidance on prerequisites or scenarios is given.

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