refresh_data

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

With no annotations, the description carries the full burden. It discloses a key behavior: 'Runs as a subprocess so the server holds no DB handle during rebuild.' This is valuable, but it does not mention whether the rebuild is destructive, if there are any downtime implications, or how failures are handled.

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 two sentences long, front-loaded with the action ('Download latest nflverse data and rebuild the warehouse'), and adds a relevant time/process note. Every word earns its place.

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 tool that rebuilds the entire warehouse, the description covers the basic action and a key implementation detail (subprocess), but omits important context: what the 'full' parameter does, prerequisites, side effects on existing data, and whether it is safe to run during active queries. The ~1-2 min estimate is helpful but not sufficient for a potentially disruptive operation.

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 one parameter 'full' with no description, and the tool description does not mention it at all (schema coverage 0%). The description fails to clarify what 'full' means (e.g., full vs incremental refresh), leaving the agent unable to make an informed decision about parameter usage.

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 tool's function: 'Download latest nflverse data and rebuild the warehouse.' It uses specific verbs and resources that distinguish it from siblings like query_warehouse and data_status.

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 implies when to use the tool (to refresh data) but does not explicitly state when it should be used in relation to alternatives. No exclusions or alternative tool references are provided, and the ~1-2 min time estimate hints at a cost but not a clear 'use when' directive.

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