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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context such as what is generated, how the draft is returned, or any prerequisites; "client and server side from freedailypro" is not useful behavioral disclosure.

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?

It is short, but the single sentence is under-specified and includes the confusing phrase "client and server side from freedailypro," which does not earn its place. The useful information is not front-loaded beyond a restatement of the document type.

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 with four required parameters, no parameter descriptions, and no output schema, the description is not complete enough to help an agent call it correctly. It provides no explanation of required fields, expected output, or generation behavior.

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 four required parameters (borrower, lender, amount, due) with 0% description coverage, and the tool description does not mention any of them. It completely fails to compensate for the undocumented 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?

The description largely restates the tool name, saying only that it is a promissory note draft, with no verb or useful scope. The phrase "client and server side from freedailypro" is unexplained vendor boilerplate and does not clarify what the tool actually does.

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?

There is no guidance on when to use this tool versus sibling document-draft tools such as business_nda_draft or business_lease_draft. It gives neither context nor exclusions.

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