Auth: состояние OAuth-токена (без секретов)

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

Description adds value beyond readOnlyHint=true: clarifies token is never returned, explains probe behavior and possible side effects (refresh). No contradiction with annotations.

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?

Description is moderately sized, front-loaded with purpose, each sentence adds value. Slightly verbose in the middle but still effective.

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 tool (one optional param, output schema exists), description covers all needed aspects: purpose, behavior, parameter details, relationship to siblings. Fully complete.

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?

Schema has 100% description coverage, but description expands on 'probe' parameter by explaining what triggering getToken means (may cause refresh) and default value. This adds meaningful context.

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?

Clearly states it reports metadata of OAuth token (present/absent, expiresInSec, last error) and explicitly distinguishes from auth_* tools that expose the token itself. The verb 'Сообщает' is specific.

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?

Provides explicit when-to-use (for metadata) and when-not-to-use (for token, use auth_*). Explains default behavior (no forced refresh) and condition for refresh (probe=true). Also mentions auth_* tools are hidden by default.

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