refresh_datasource

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

No annotations are provided, so the description carries full burden. It mentions 'trigger a refresh' and 'Refresh job status', suggesting potential async behavior, but lacks details on execution time, failure modes, or side effects.

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 short and uses a structured docstring format (Args/Returns). It avoids unnecessary words, though the docstring could be more informative.

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?

For a simple one-parameter tool, the description is adequate but not thorough. It mentions the return value ('Refresh job status') but omits behavioral details like whether the call is blocking. The presence of an output schema partially compensates, but the parameter is still under-described.

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?

With 0% schema description coverage, the description fails to add meaning beyond the schema. The parameter 'datasource_id' is only listed without explanation of how to obtain it (e.g., from get_datasource).

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 the action ('trigger a refresh') and resource ('data source extract'), making the tool's purpose straightforward. While it distinguishes from siblings by the unique 'refresh' action, it does not explicitly differentiate from other tools.

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 explicit guidance on when to use this tool versus alternatives like get_datasource_extract_info. The description implies usage for refreshing extracts but provides no prerequisites or context.

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