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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description consistently describes a GET request. The description adds the endpoint string but does not disclose additional behavioral details such as error cases, required authentication, or response shape; the annotation carries most of the safety context.

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 two short sentences with no filler. The core operation is front-loaded, and the endpoint reference is compact and useful without bloating the description.

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 simple one-parameter, read-only tool, the description is nearly complete: it identifies the operation, the parameter, and the API endpoint. It does not describe the return value or error behavior, but given the low complexity and the readOnlyHint annotation, this is a minor gap rather than a critical one.

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 coverage is 100%: the single parameter task_id is already documented as 'The task id.' The description repeats that the lookup is 'by id' but adds no format, constraints, or additional meaning beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Get a single task by id.' It also names the exact Keap endpoint, which clearly distinguishes this retrieval tool from create/list siblings like keap_create_task and keap_list_tasks.

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 phrase 'single task by id' gives clear context for when to use this tool: when the agent already has a task_id and needs exactly one task. It does not explicitly mention alternatives or exclusions, but the single-task framing is enough to separate it from list operations.

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