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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the repeated "Read-only" sentence earns little credit. The genuinely additive detail is the null-return contract when a task isn't visible to the caller, which tells an agent how to interpret an empty result rather than an error — but it stops short of describing the returned task shape or visibility/authorization rules.

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?

Three short sentences, front-loaded with the operation and scope, followed by the safety trait and the null case. Nothing is padded or buried; only the "Read-only" clause mildly duplicates the annotations.

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 one-parameter read tool with strong annotations and no output schema, the definition covers the essentials: what is fetched, its scope, and the not-found semantics. Only the id format/type ambiguity is left entirely to 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 0% for the single task_id parameter, so the description must carry the meaning. It clarifies that the id identifies a task in the caller's workspace, but says nothing about the accepted integer-or-string duality, whether ids from other workspaces are rejected, or how an unknown id differs from an invisible one.

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 definition opens with a specific verb+resource pair: "Read a single personal task by id," and scopes it to "the caller's workspace," which separates it from workspace-agnostic sibling getters. It does not explicitly name the mutating siblings (update_task, delete_task, create_task) it complements, but the verb makes the read intent 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?

Usage is implied rather than stated: an agent infers it should call this when it already holds a task id. There is no explicit when-not guidance (e.g., when to use a task-list or search tool instead) and no prerequisites or permissions context.

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