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

Annotations provide only destructiveHint=true and a title, so the description must carry the behavioral load. It correctly labels the operation as a WRITE and names the underlying endpoint, but says nothing about side effects such as whether notification emails fire by default or what permissions are required. Note the destructiveHint=true annotation is unusual for a create operation, but the description does not contradict it.

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 compact sentences with no waste; the write-nature and core purpose are front-loaded, then the parameter-sourcing hint. 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 an 8-parameter mutation tool with no output schema and thin annotations, the description covers purpose, optional linkage, user-ID sourcing, and the endpoint. The remaining gaps (default notification behavior, permission requirements) are minor since send_notifications is documented in the schema.

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 the baseline is 3, but the description adds genuine value by explaining how to obtain assignee_user_id (via bloomerang_get_current_user or existing tasks) and that constituent linkage and assignment are optional. It does not restate the enum semantics for channel/purpose, which the schema already covers.

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+resource ('create a follow-up task') plus its optional scoping ('tied to a constituent and assigned to a user'), which differentiates it from the sibling create_note and create_interaction tools. The 'WRITE:' prefix and the raw endpoint (POST /task) make the operation unambiguous.

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?

It gives a concrete sourcing hint for the assignee parameter ('find user Ids via bloomerang_get_current_user or existing tasks'), which is a real routing cue. However, it offers no when-to-use-this-vs-alternatives guidance relative to bloomerang_create_note or bloomerang_create_interaction, which are the closest siblings.

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