cloud_tsks_get

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

With no annotations, the description must convey behavioral traits. It only states 'Get task' without disclosing whether the operation is read-only, has side effects, or requires any permissions. There is no mention of rate limits or data freshness.

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 extremely short ('Get task') followed by a parameter list. It is concise but under-specified. The parameter list could be formatted more efficiently, but there is no fluff.

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?

Given no output schema and no annotations, the description should provide more context about the return value or behavior. It fails to explain what the tool returns (e.g., task object) or any edge cases (e.g., task not found). Incomplete for a simple retrieval tool.

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%. The description adds minimal value by restating parameter names with trivial clarifications (e.g., 'task_id: Task ID' is redundant). For 'extra_headers', 'Send extra headers' offers no additional meaning beyond the name.

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' clearly indicates the action and resource. It distinguishes from siblings like 'cloud_tsks_ls' (list tasks) by implying retrieval of a single task. However, it lacks specificity about what a 'task' represents in this context.

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?

No guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, limitations, or when not to use it. Sibling tools like 'cloud_tsks_ack_all' and 'cloud_tsks_ack_one' are not compared.

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