analyze_zypper_conf

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

The readOnlyHint annotation already establishes that the operation is safe, and the description goes beyond by disclosing platform-specific behavior, conditional output based on focus, and the presence of warnings and optimization recommendations for certain focus values. This provides substantial context without contradicting the annotation.

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 moderately sized but each sentence contributes value: purpose, output summary, platform constraint, and concrete examples. The examples are slightly redundant with the schema's enum definitions, but they add behavioral nuance, so there is minimal waste.

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 single-parameter tool with read-only behavior, the description covers the essential aspects: what is parsed, what is returned, supported focus values, and output variations. It does not specify the exact return format, but the absence of an output schema and the tool's simplicity make this acceptable.

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 fully documents the focus parameter with enum values and descriptions, but the description adds practical meaning—e.g., 'ignored_packages' returns warnings for critical ones, and 'parallel_downloads' includes optimization recommendations. This enriches the parameter semantics beyond the schema's basic definitions.

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's function: parsing and analyzing zypper.conf, with a specific list of output categories. It distinguishes itself from sibling tools by targeting this particular configuration file, and the platform constraint ('Only works on SUSE Linux') further clarifies its scope.

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 gives clear context for when to use the tool—when zypper.conf settings need analysis—and includes a platform limitation. However, it does not explicitly mention alternatives or conditions under which a different tool would be preferable, so it lacks exclusionary guidance.

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