get_config_guide

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

没有注解，描述承担全部披露责任。'查看'暗示只读操作，且列出配置说明的具体范围（Sci-Hub、EZProxy、TDM API），让代理了解返回值内容。未明确说明不修改任何设置，但动词稳定性足够。

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的工具，描述完整说明工具用途和返回内容主题，足以让代理正确调用，无需额外上下文。

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?

该工具无参数，描述无需补充参数语义。按照准则无参数时基线为4，且描述与空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?

描述使用明确的动词'查看'和资源'插件配置说明'，并列出具体涵盖的主题（Sci-Hub、EZProxy、TDM API），区别于 get_settings 等实际配置工具。清晰标示了此工具是查看说明而非修改配置。

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?

虽然没有显式说明何时使用或与其他工具对比，但'查看插件配置说明'自然暗示使用场景。缺少对 get_settings/set_settings 等替代工具的排除说明，但零参数简单工具使上下文基本明确。

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