doctor

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

With no annotations provided, the description carries the full burden. It discloses a key safety behavior—'Never prints secret values'—and implies a read-only nature by using 'Report'. It also indicates the output format switch via json:true, adding transparency about behavior without contradicting any 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?

The description is a compact three sentences: the first front-loads the primary action and scope, the second gives a usage hint, the third states a critical safety guarantee. Every sentence earns its place, with no filler or repetition.

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 covers the tool's purpose, contents, output format option, and a key behavioral constraint. It does not formally specify the return schema or list field types, but given there is no output schema and the tool is a general status reporter, the description is enough for an agent to understand its functionality.

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 only defines a boolean 'json' parameter with no description coverage. The description compensates by explaining exactly what 'json:true' does ('structured output'), which is more meaningful than the schema alone. It does not specify defaults or return format details, but the essential semantic is conveyed.

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 a specific action ('Report Vibecoders status') and enumerates the exact contents covered (capabilities, delegation providers, mounted servers, optional API keys, tool groups, session's lane). This clearly distinguishes it from sibling tools like delegate or list_providers, which have narrower scopes.

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 provides clear context for when to use it: to get a comprehensive status report. It also instructs how to request structured output ('Pass json:true'). It does not explicitly mention alternatives or exclusions, but its scope is self-evident from the enumerated fields.

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