Auth Probe

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

With no annotations, the description must carry the full burden. It mentions 'without secrets' implying safe operation, but does not explicitly state read-only behavior, side effects, or whether it is safe to call repeatedly. Agent must infer from 'read' verb.

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?

Single sentence, no wasted words. Efficiently conveys core action. Appropriate for the tool's simplicity.

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?

The description is sufficient for a simple probe tool, but lacks details on output format, success/failure indicators, or error handling. Since there is no output schema, the description should provide at least some behavioral hints.

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?

No parameters exist, and schema coverage is 100%. The description adds little beyond the schema since it does not explain return values or behavior. Baseline of 3 is appropriate for a no-param 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 it probes live auth using a minimal read operation on workbooks list, which clearly identifies the tool's purpose. However, it could be more explicit about what 'probe' means (e.g., verifying authentication validity). Distinguishes from siblings like dl_list_workbooks by focusing on auth checking.

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?

No guidance on when to use this tool versus alternatives. Among many sibling tools (e.g., dl_diagnose, dl_runtime_status), there is no indication of its specific role or prerequisites for use.

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