build_explore_url

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

无注解；描述未说明权限、URL 拼接细节、是否只读/审计操作，也未有输出表单。

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?

描述简短完整，但缺少结构化后缀/字段说明。

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?

无输出 schema 或返回字段；9 个可选参数未描述其生成的 URL，未说明是否需要先列举数据源/project。

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 覆盖仅 11%；除 range 默认 15m 外全部参数无说明，无法理解 datasourceUid、keyword、level 如何参与生成 URL。

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?

描述明确指定“生成 Grafana Explore 深链”，动词+资源清晰，但与同级日志查询类工具的区别未显式说明。

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?

未说明使用时机（AI 结论后一键核对）也未提及备选工具，缺乏排除性指引。

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