Submit manual daily data

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly discloses that the tool validates and upserts data and that it 'returns counts only, not the submitted dataset,' which is highly useful. It does not detail validation rules or side effects, but the primary behavioral expectations are covered.

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?

Two sentences with no filler: the first states the operation and scope, the second clarifies the return behavior. It is front-loaded and every sentence 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?

Given the single `records` array parameter and a well-defined nested schema, the description is largely sufficient. It tells the agent what data is being submitted, the write behavior, and the response shape. Minor gaps such as explicit sibling routing and field-level format details are not severe enough to reduce completeness.

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 schema has 0% description coverage, so the description should compensate. It adds some meaning by listing acceptable metric categories like 'spot, inventory, operating-rate,' which clarifies the `metric` field, but it does not explain the required per-record fields (trade_date, symbol, metric, value) or value formats. The nested schema remains self-explanatory enough for a 3.

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 operation ('Validate and upsert') and the resource ('structured spot, inventory, operating-rate, or other daily metrics'). The title and tool name also reinforce that this is for manual daily metric submission, which distinguishes it from the report/research-focused sibling 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?

The phrase 'spot, inventory, operating-rate, or other daily metrics' implies the tool is for submitting daily metric data, and the title suggests manual entry. However, there is no explicit guidance on when to prefer this tool over siblings like report_save or research_search, nor any stated exclusions.

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