check_credentials

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations by warning that a successful result does not guarantee publishing permission, which is critical for agent decidsion-making. No contradiction with annotations exists.

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 sentence with the action and target front-loaded, and the important caveat delivered compactly after a semicolon. Every clause adds value, and there is no redundant or filler wording.

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 zero parameters, clear annotations, and an output schema present, the description fully covers the essentials: what is verified and a key behavioral limitation. An agent has enough context to select and invoke this tool correctly.

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 tool accepts zero parameters, so the semantic baseline is 4 and no parameter explanations are necessary. The description appropriately focuses on behavior rather than fields that do not exist.

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 states a specific action ('验证' / verify) targeting a specific resource ('公众号凭据和 IP 白名单'), which clearly distinguishes it from data-retrieval or mutation siblings such as get_server_ips and create_draft. The caveat about publishing permission further sharpens its scope.

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?

The description implies this is a pre-flight check before publication and notes a limitation, but it does not explicitly state when to use it instead of alternatives or what conditions would make it unnecessary. Since no sibling tool duplicates this exact function, the gap is minor.

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