Warehouse freshness (last_load)

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

Beyond the readOnly/idempotent annotations, the description explains meaningful behavioral context: the warehouse is 'only a DAILY snapshot', Last_Load is 'the only reliable data is fresh signal', and Backup_Taken defines accuracy bounds. It also warns against presenting day-old data as current, which is valuable operational nuance.

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 well-structured and each sentence adds value: object identity, field semantics, usage scenarios, cautionary guidance, and a pointer to further documentation. It is information-dense without padding.

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 tool's simplicity (no parameters, read-only, output schema present), the description fully covers what an agent needs to decide when to call it and how to interpret its results. It even includes a pointer to the broader model guide for additional context.

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 has zero parameters, so the schema provides no constraints. The description explicitly states 'No parameters', which is sufficient for the agent; no additional parameter semantics are needed.

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 states a specific verb and resource: 'Return the warehouse freshness markers from the special object warehouse_last_load'. It clearly differentiates the tool from siblings by explicitly noting the object is 'NOT a wh_ view and does NOT appear in list_views', making its unique role unmistakable.

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 gives clear when-to-use guidance: 'Use it to check how current the data is, and as the first smoke test after deploy' and advises checking it first for time-critical questions. It does not explicitly name an alternative tool like query for row-level data, but the priority and purpose are well stated.

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