Add discovery lead

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

With no annotations provided, the description carries full disclosure burden. It adds valuable behavioral details: Date Found defaults to today, Status defaults to 'Open', and it 'Backs the file up first'. These go beyond the schema and reveal side effects and defaulting behavior, though it does not mention return values or error handling.

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 with no fluff. It front-loads the core action and then supplies key details in a compact, scannable manner. 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?

For a simple append operation with no output schema, the description covers purpose, required vs optional inputs, defaults, and a safety behavior (backup). It does not mention return values, but that is easily inferable for an append tool and is not a critical gap. The description is complete enough for an agent to invoke correctly.

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?

Although schema coverage is 100%, the description adds meaning by providing concrete field examples (Salary, Job Link, 'Match Assessment') and explaining default behavior for Date Found and Status, which are not explicit schema properties. This enriches understanding beyond the structured definitions.

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 'Append a new lead to the discovery sheet' with a specific verb and resource, clearly distinguishing it from sibling update/delete/list operations. The title 'Add discovery lead' reinforces this purpose without ambiguity.

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 'Append a new lead' implies usage for adding new entries, but the description does not explicitly state when to use this tool versus alternatives like discovery_update or discovery_delete. There are no exclusions or alternative tool mentions, making the guidance only implied.

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