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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false. The description adds real value beyond those: it discloses the connection-requirement failure path (error points the user to Wavelength settings) and what the payload contains. It does not discuss reversibility of the created record/note, so it stops short of a 5.

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, both earning their place, with the mode-selection condition front-loaded. The closing sentence on connection errors is slightly tangential but still actionable, so it is well-sized rather than padded.

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?

With no output schema, no nested objects, and full schema coverage, the description supplies everything an agent needs: the two modes, the triggering parameter, the content of the generated text, and the auth/connection failure behavior. Nothing material is missing.

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 coverage is 100%, so baseline is 3, but the description adds meaning by explaining that presence or absence of sys_id switches the tool's behavior, and by describing what the summary text contains and how the flow link is appended. That is semantic value beyond the schema's field-level text.

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?

States a specific verb (add/send a flow) and resource (ServiceNow record) and distinguishes its two operating modes: work note on an existing record when sys_id is supplied, or a new record when it is omitted. An agent can distinguish it from the many send_flow_to_* siblings by the ServiceNow target alone.

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?

Gives clear conditional guidance for choosing between the two modes (provide sys_id vs. omit it) and the schema points to find_servicenow_records for obtaining a sys_id. It does not explicitly name sibling alternatives like send_flow_to_jira, but the resource routing is unambiguous.

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