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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so safety basics are covered. The description adds valuable non-obvious behavior: assigning others notifies them, confirmation is required by default and is configurable, and a scoped Cotlet API key is required.

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 confirmation policy is repeated three times ('so you confirm by default', 'By default you confirm each call', 'confirm with the user before each call'), which is redundant. The leading 'Buildertrend:' prefix also duplicates the title. Purpose is front-loaded, but the repetition wastes space.

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 create tool with no output schema and full annotation coverage, the description covers the important behavioral surface: side effects on other people, confirmation requirements, and auth needs. It omits any mention of the response shape, but with no output schema that is a minor gap.

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?

With 100% schema description coverage, the schema already documents all six parameters, including the ISO 8601 deadline and assignee semantics. The description only restates that assignees, deadline and checklist are optional, adding no syntax or format detail beyond the schema, so the baseline of 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 and resource ('Creates a task on one job') and enumerates the notable attributes (assignees, deadline, checklist). It is clearly distinguishable from the read-side sibling buildertrend_list_tasks, though it does not name that sibling explicitly.

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?

Provides operational guidance about the confirmation step ('confirm with the user before each call'), which is genuinely useful. However it never states when to choose this tool over alternatives or prerequisites like needing a valid job_id from list_jobs beyond what the schema already says.

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