obs_log_datasources

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

With no annotations, the description must disclose behavior. It only mentions listing data sources for mapping, but does not describe if the list is full or filtered, if it requires specific permissions, or if it returns any live status. The behavioral disclosure is minimal and insufficient for a tool with no annotation fallback.

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 a single, concise sentence that front-loads the purpose. It earns its place by clarifying the tool's intent (mapping confirmation), but could be slightly more efficient.

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?

The tool has one parameter, no annotations, and an output schema (not shown). The description partially explains the tool's purpose but lacks key context such as output structure, required permissions, or when to use sibling tools. Given the simplicity, it is minimally adequate but could be more self-sufficient.

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%, so the description must compensate. It mentions '指定日志平台' (specified log platform) which hints at the 'region' parameter, but adds no detail about valid values or format. The schema defines one required parameter with no additional info, so the description adds some context but not enough to fully interpret the parameter.

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 explicitly states the tool lists Loki data sources for a specified log platform, and clarifies its purpose is to confirm the mapping between environment names and data source names. The verb '列出' (list) and resource 'Loki 数据源' are clear, but it does not differentiate from siblings that also query log platforms like obs_log_query.

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 is provided on when to use this tool vs. alternatives like obs_log_query. The description implies first-step use for mapping, but does not state that obs_log_query should be used for actual log searching or that this tool is a prerequisite.

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