youtube_cookie_status

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

With no annotations, the description carries the full burden. It usefully conveys that this is a read/diagnostic operation that both reports a location and validates auth, but it does not disclose whether the authentication test performs network calls, mutates or refreshes cookie state, or requires any setup.

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?

A single compact sentence that front-loads the two things the tool does with no filler. Every clause earns its place.

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?

There is no output schema and no annotations, so the description is the only source of information about results. It hints at output (storage path, pass/fail auth test) but does not describe the return format or how to interpret the authentication result, leaving a meaningful gap for a diagnostic 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?

The tool takes zero parameters, so the schema is trivially complete and the baseline for a no-parameter tool applies. There is nothing for the description to clarify beyond that.

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 names two concrete behaviors: reporting cookie storage location and testing whether stored cookies authenticate. This is a specific verb+resource statement that an agent can act on, and it implicitly separates this diagnostic tool from the mutating sibling youtube_cookie_set.

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?

Usage is only implied: it is a diagnostic to run when you want to know whether stored cookies still work. There is no explicit when-to-use, no stated prerequisite (e.g., run before youtube_cookie_set or prior to authenticated calls), and no mention of the sibling it complements.

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