contacts_get_task

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds zero behavioral context—it does not mention that this returns a single task, whether it requires existing records, or any special behavior. It contributes nothing beyond the annotations.

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 words with zero informational content. This is not concise specification; it is under-specification. It fails to provide any structure or front-loaded details that would help an agent.

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 no output schema and sibling tools that include get_all_tasks, delete_task, and update_task, the description is incomplete. An agent has no idea what the return value looks like, what constitutes a valid task, or what scoping is applied. The description is inadequate for a tool with two required parameters.

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%, with both parameters (taskId and contactId) documented as 'Task Id' and 'Contact Id'. The description adds no additional meaning, but the baseline of 3 applies because the schema fully explains the parameters.

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 Task' is essentially a tautology of the tool name. It lacks any specificity about what kind of task, what resource it operates on, or how it differs from sibling tools like contacts_get_all_tasks. An agent cannot distinguish this from other task-related tools without reading the schema.

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 on when to use this tool versus alternatives. No mention of prerequisites, context, or exclusions. The sibling list includes similar tools like contacts_get_all_tasks and contacts_delete_task, but the description provides no decision criteria.

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