create_client_note

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

The description incorrectly states 'All three fields ... are required' when the schema shows four required parameters (client_id, note, subject, date). This is misleading and contradicts the schema, harming transparency. No annotations exist to compensate.

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 short but contains an inaccuracy (three vs four fields). It is not concise in the sense of being correct and to the point; the error forces the agent to cross-check with schema.

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?

The description lacks crucial context: it misstates the number of required fields, does not mention the client_id parameter, and provides no information about return values (even though an output schema exists). It is incomplete for a creation tool with 4 required parameters.

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 description adds format guidance for 'date ISO 8601' beyond the schema's basic string type, but it omits the client_id parameter entirely. With 0% schema description coverage, the description should explain all parameters; it only addresses three of four, leaving client_id unexplained.

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 'Create a note on a client', which clearly identifies the action and resource. However, it fails to mention that a client_id parameter is required, which is a critical omission. The purpose is clear but incomplete.

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?

No guidance is provided on when to use this tool versus alternatives such as create_case_note, create_company_note, or the generic create_note. The description offers no context on prerequisites or scenarios.

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