doctor

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

Describes the three checks and their reporting format, but does not explicitly state that the tool is read-only or if it has any side effects. Given no annotations, the description is transparent enough for a diagnostic tool, but could mention non-destructiveness.

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?

Highly concise with two short sentences. First sentence front-loads usage context, second describes output. No unnecessary words 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?

Given the tool's simplicity (no params, clear purpose, output schema exists), the description fully covers when and why to use it, what it does, and what to expect. No gaps.

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, so schema coverage is 100%. Description adds meaning by detailing the checks and output format, beyond the empty schema. Baseline 4 for zero params is appropriate.

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 the tool performs three diagnostic checks (osxphotos install, Photos library readability, Full Disk Access) and returns ok/warn/fail results with advice. Distinguishes from siblings like health-check by targeting permission errors and full setup diagnostics.

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?

Explicitly specifies when to use (permission errors or before querying/exporting) and when not to (lightweight smoke test, use health-check instead). References sibling tool health-check for alternative.

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