ShowLogStreamShards

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

No annotations are present, and the description provides zero behavioral detail such as whether the operation is read-only, what permissions are required, or what side effects occur. The description carries the full burden of disclosure and fails entirely.

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 one sentence long, but it is tautological and provides no substantive information. This is under-specification rather than effective conciseness.

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, and a description that simply restates the operation name, the tool lacks essential context needed for correct invocation, such as what identifiers are required and what the response will contain.

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 does not mention any of the four parameters. Schema coverage is only 50% and the description does not compensate for the undocumented group_id and stream_id parameters, providing no additional meaning beyond the schema.

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 as 'Huawei Cloud LTS operation ShowLogStreamShards' and does not specify what the operation actually does (e.g., retrieving shard information for a log stream). It does not distinguish this tool from siblings that also relate to log streams and cursors.

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 such as ShowCursorByTime or ListLogStreams. 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.