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

Annotations already declare readOnly=false, destructive=false, and openWorld=false, so safety is covered. Beyond that, the description adds the confirmation-message convention, which is genuinely useful behavioral context, but it says nothing about defaults, participant handling, or what a created task looks like.

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, front-loaded with the core action, with no wasted prose. The embedded quote format is slightly awkward to parse but does not add fluff.

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 four parameters, no parameter descriptions in the schema, and no output schema, the description needs to carry more weight than it does. An agent still lacks the meaning of priority and participants, and there is no statement of what happens on duplicate or invalid input.

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 0% across four parameters, so the description must compensate and largely does not. It implicitly covers title and dueDate ("Omit the due day when absent"), but says nothing about priority values or participants, leaving half the parameters undocumented anywhere.

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?

"Create a task in Lemongraph" gives a specific verb (create) and resource (task), which is unambiguous against siblings like complete_task or get_today. It does not explicitly compare itself to any alternative, so it falls short of the top tier.

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 definition offers no guidance on when to use this versus alternatives, no prerequisites, and no exclusions. The only instruction is about the confirmation phrasing, which is output style rather than usage guidance.

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