check_bilibili_credentials

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

Description discloses that it does not expose Cookie values, a key security behavior, and that it returns next_steps for setup if credentials are missing or invalid. Since no annotations are present, this provides necessary behavioral context.

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?

Two sentences, no filler, front-loaded with main purpose. Every sentence adds value: purpose, security note, and return value.

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?

Given zero parameters and no output schema, the description covers purpose, security, and return logic. The exact format of 'next_steps' is not detailed, but this is acceptable for a simple check tool.

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?

With no input parameters, schema coverage is 100%, and the description confirms zero inputs implicitly. Baseline score of 4 is appropriate as no parameter details are needed beyond this.

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?

Description clearly states verb 'Check' and resource 'Bilibili credentials', specifies it checks configuration and login status without exposing cookies, and mentions return of next_steps. Distinguishes from sibling 'get_credential_setup_instructions' which likely provides setup guidance rather than status checks.

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 usage for credential status verification, but does not explicitly state when to use this tool versus alternatives like 'get_credential_setup_instructions'. No when-not-to-use guidance is provided.

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