teamleader_notes_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the creation action and linkage, without addressing authorization, side effects, or what happens upon success or failure. This leaves the agent with little beyond the obvious write operation.

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 a single concise sentence that front-loads the verb and object, with no wasted words. The parenthetical examples add useful clarity without bloating the text.

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 low-complexity three-parameter create operation, the description adequately covers the core purpose and linking concept. The absence of an output schema and annotations means return/error behavior is not explained, but this is a minor gap given the straightforward nature of the tool.

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 input schema already fully describes all three parameters at 100% coverage, so the description does not need to repeat them. The mention of 'contact, company, deal' reinforces the subject_type examples but adds no new semantic detail beyond what the schema already provides, earning the baseline score.

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 uses the specific verb 'Create' with a clear resource ('a note') and adds the key constraint that it is linked to a subject, with examples like contact, company, and deal. This distinguishes it from sibling tools such as teamleader_notes_list and other create tools.

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 description clearly implies when to use the tool: when creating a note tied to a contact, company, or deal. It does not explicitly state when not to use it or name alternative tools, but no direct sibling alternative for note creation exists, so the context is sufficient.

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