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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the write semantics are known. The description reinforces this with 'WRITE:' and the POST /tasks endpoint, which is consistent, but adds nothing about side effects such as whether duplicate tasks are created on retry or what gets returned.

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 short sentences, zero filler. The verb/scope comes first, followed immediately by the required-field constraint and endpoint. Every clause 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 6-parameter mutation with no output schema, the description covers purpose, required inputs and the attachment model. It could still mention the return value (e.g. the new task id) since no output schema exists, which keeps it from a 5.

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 description coverage is 100%, so all six parameters are documented in the schema itself, including the target_type enum and the cross-reference to freshsales_list_owners. The description only restates which fields are required, which is already encoded in the required array; baseline 3 applies.

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 ('create'), a specific resource ('a task (to-do)'), and the scope of attachment (contact, account or deal). The resource name alone cleanly separates it from sibling creators like freshsales_create_note or freshsales_create_appointment.

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 'WRITE:' prefix and required-field list imply this is the tool for creating tasks, but the description never says when to prefer it over update_task or create_note, nor any prerequisites (permissions, dedupe on existing tasks). Usage is inferable rather than stated.

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