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 'get', which weakly implies a read operation, but it does not mention read-only behavior, response format, error conditions, authentication needs, or what the returned task object contains.

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 short, front-loaded sentence with no filler or redundant clauses. It is concise, though its brevity comes at the cost of useful operational context.

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?

The tool is simple, but the description omits key context: that it retrieves a single task by task_id within an organization, what the response looks like, and how it differs from the closely named commsharbor_platform_crm_tasks_get sibling. The absence of output schema means more descriptive burden falls on the description, which is unmet.

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 schema already documents both required parameters. The description adds no parameter-level meaning beyond what the schema provides, which aligns with the baseline score of 3 for high schema coverage.

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 'get CRM task' is a near-verbatim restatement of the tool name commsharbor_crm_tasks_get, adding no new information. It does not differentiate this single-task retrieval from commsharbor_crm_tasks_list or the similarly named commsharbor_platform_crm_tasks_get.

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?

There is no guidance about when to use this tool versus alternatives. Siblings such as commsharbor_crm_tasks_create, commsharbor_crm_tasks_list, and commsharbor_platform_crm_tasks_get exist, but the description provides no context for selection or exclusion.

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