get_task_definition

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

No annotations are provided, so the description carries the full behavioral-disclosure burden, but it only repeats the tool name. It does not state whether this is a read-only lookup, what permissions are required, what a missing task returns, or any other behavioral trait. This is effectively no behavioral transparency.

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, but it is under-specified rather than appropriately concise. It contains no wasted words, yet it fails to front-load any useful information beyond the tool name.

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, no annotations, two undocumented required parameters, and many closely related sibling tools, the description is completely inadequate. An agent lacks the information needed to understand what task definition is returned, by what identifier, or how this differs from list_task_definitions.

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?

The schema has 0% description coverage and two required parameters, robot_sn and fusion_task_id. The description provides no meaning, format, relationship, or usage guidance for either parameter, so it fails to compensate for the schema 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?

The description is only a bilingual restatement of the tool name: '查询任务定义 / Get task definition'. It states the verb and resource but adds no scope or distinction from siblings like list_task_definitions, create_task_definition, or update_task_definition. This fits the definition of a tautological restatement rather than a useful purpose statement.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as list_task_definitions for listing or the create/update/delete siblings. The agent is given no information to decide when this tool is appropriate.

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