diagnose_system

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

Annotations indicate readOnlyHint=true. The description expands on this by stating the tool is for monitoring and lists diagnostic actions, but does not mention any destructive behavior or additional constraints like required permissions.

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 single clear sentence with a category tag, listing actions concisely. No extraneous information.

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?

For a simple diagnostics tool with two enum actions and one optional parameter, the description is sufficient. No output schema exists, but the actions' output is generally well-understood.

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 description coverage is 100%, so baseline is 3. The description briefly explains the two actions and mentions the 'lines' parameter for boot_logs, adding some context beyond the schema.

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 clearly states the tool performs unified system diagnostics for systemd-based systems, listing specific actions (failed_services, boot_logs). It distinguishes from sibling tools, which focus on package management and other system tasks.

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 includes '[MONITORING]' and 'Works on systemd-based systems only,' providing context for when to use the tool and when not (non-systemd systems). No explicit alternatives are mentioned, but siblings are distinct enough.

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