ShowCursorTime

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses nothing about side effects, read-only vs. mutating behavior, cursor semantics, or any operational characteristics. The description adds zero value beyond the structured fields.

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. A single tautological sentence does not earn its place because it provides no actionable information.

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?

This tool has 6 parameters, no output schema, no annotations, and a complex sibling context. The description is completely inadequate for an agent to understand what the operation does, when to invoke it, or how to construct a valid request.

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?

With 6 parameters and only 33% schema description coverage, the description needed to compensate by explaining parameter roles. Instead, it offers no parameter information at all. The only useful parameter descriptions come from the schema itself (region and project_id overrides), which are not sufficient.

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 merely restates the tool name and cloud service ('Huawei Cloud LTS operation ShowCursorTime') without a specific verb or resource. It is tautological and provides no information about what the tool actually does, failing to distinguish it from siblings like ShowCursorByTime.

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 versus alternatives. No context, prerequisites, or exclusions are provided, leaving the agent without any basis for selection among the many sibling tools.

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