echopath_get_task

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

No annotations are provided, so the description carries the full burden. It does signal a read-style operation and discloses the returned fields, which is useful, but it says nothing about permissions, whether a task must be started/resumed first, error behavior for unknown run_id, or freshness of the status snapshot.

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?

A single front-loaded sentence with no filler; the returned fields are listed compactly. It is efficient, though the terseness leaves no room for the usage and identifier context the tool needs.

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?

An output schema exists, so the description need not restate return values, and for a one-parameter read tool it is close to sufficient. The remaining gap is the undefined run_id semantics and lack of any routing guidance against the many sibling read tools.

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% and the single parameter run_id is undocumented in both schema and description. The description's use of 'task' versus the parameter name 'run_id' leaves the identifier relationship ambiguous, so the description does not compensate for the coverage gap.

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 and resource ('Return a single tracked task') and enumerates the payload (status, activity, final result), so the agent knows exactly what it retrieves. It does not distinguish itself from the neighboring read tools such as echopath_get_status or echopath_get_session, so sibling differentiation is absent.

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 call this versus echopath_get_status, echopath_list_runs, or echopath_get_session, all of which are plausible alternatives for retrieving task state. No prerequisites, polling advice, or exclusions are given.

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