ingest_form16

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

No annotations are provided, so the description carries the full burden. "Store" implies a write, but the description does not say whether the operation is idempotent, whether duplicate submissions for the same employer TAN overwrite, dedupe, or error, whether validation runs, or what the response contains.

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, no filler, with the identity of the resource and the per-employer cardinality rule front-loaded. The clause "that you have read and mapped into the Form16Data schema" is slightly dense but earns its place by constraining the input shape.

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 single-object ingest tool with no output schema and no annotations, the definition covers what to send but not what happens as a result—no confirmation format, no duplicate-handling rule, no failure behavior. The rich schema covers field requirements, so the remaining gap is operational rather than structural.

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 description coverage is 0% at the property level, so the description must compensate. It adds one genuinely useful semantic point—that the payload is the output of a read-and-map step adhering to Form16Data—but says nothing about field expectations such as monetary units, why amounts accept both number and string, or the assessment_year pattern, all of which are left to the schema.

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?

"Store one employer's Form 16" gives a specific verb plus resource, and "mapped into the Form16Data schema" clarifies the input must be pre-extracted structured data rather than raw text or a file. It is implicitly distinct from siblings like ingest_ais and ingest_26as through the named document, though it never names those siblings explicitly.

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?

"Submit one call per employer" is a real usage rule and implies the tool should be called repeatedly for multiple employers rather than batched. However, there is no guidance on when to choose this over ingest_ais/ingest_26as, and no stated prerequisite that the document must be read and extracted first beyond the passing mention.

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