ListLogContext

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

No annotations are present, and the description carries the full burden of behavioral disclosure. The description reveals nothing about whether this operation is read-only, what permissions are needed, side effects, limits, or return characteristics.

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 short but this is under-specification, not conciseness. It is a single placeholder sentence that carries no useful information, while the tool's complexity (nested body object, multiple parameters) demands more explanation.

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 five parameters, a nested body structure, no output schema, and no annotations, this description is completely inadequate. An agent could not infer the operation's purpose, parameters, or behavior from this text.

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 description adds no parameter meaning. Schema coverage is only 40% (region and project_id have descriptions), and the body object with time__, line_num, scroll_id, forwards_size, backwards_size remains unexplained. The tool name suggests 'context' but the meaning and purpose of these parameters are not clarified.

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 'Huawei Cloud LTS operation ListLogContext' is a tautology that merely restates the tool name without explaining what the operation does. It fails to mention the verb or resource, and provides no distinction from sibling tools like ListLogs or ListLogStream.

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 use this tool or how it differs from alternatives such as ListLogs or ListLogStream. No context, prerequisites, or exclusions are provided.

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