zzz_daily_note

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

With no annotations, the description carries the full behavioral burden. The phrase 'real-time note' plus the listed outputs implies a read-only snapshot, but it does not explicitly state that no mutation occurs, that authentication is required, or what happens when no account is logged in. The account-related guidance is useful, but the behavioral profile is mostly inference.

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 compact and information-dense: the domain, resource, relevant outputs, and parameter guidance are all packed into a single sentence. There is no filler, repetitive wording, or unnecessary elaboration.

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 the simple optional parameter and lack of an output schema, the description covers the key invocation detail and even previews the returned fields. The main gap is that it does not state authentication prerequisites or behavior when zero accounts are logged in, but the account_id guidance provides enough context for most agentic flows.

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 schema describes account_id only with a type and default, and schema description coverage is 0%. The description compensates fully by explaining the exact source of the value (accounts_list) and the condition for omitting it. This is high-value guidance an agent needs before calling the tool.

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 the resource clearly: a real-time note for Zenless Zone Zero, and enumerates what it contains (battery charge, engagement, video store). It implicitly distinguishes itself from the sibling starrail_daily_note and genshin_daily_note by naming the game. It lacks an explicit verb like 'get' or 'fetch,' but the meaning is unambiguous.

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 gives concrete invocation guidance: where account_id comes from (accounts_list) and when to omit it (when only one account is logged in). It does not explicitly discuss alternatives or exclusion cases, but the game-specific phrasing makes the intended use clear relative to the sibling game-note tools.

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