faz_get_adom

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

Annotations already declare read-only/idempotent behavior, so the description doesn't need to repeat that. It adds a useful behavioral detail: an empty adom parameter falls back to FAZ_DEFAULT_ADOM. This goes beyond the schema, which provides no description for the parameter.

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 remarkably concise—two sentences that cover purpose and a key parameter behavior. It is properly front-loaded with the primary action in the first sentence and no extraneous content.

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 getter with rich annotations and an output schema, the description covers the essential purpose and a critical edge case (empty ADOM). It does not address invalid ADOM names, but that is not necessary given the annotations and output schema; the description is adequate.

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?

With 0% schema description coverage, the description fully compensates by explaining the parameter's behavior: an empty ADOM uses FAZ_DEFAULT_ADOM. It directly clarifies what the 'adom' string means and how the default value works, which is essential for correct invocation.

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 a specific action ('Get one ADOM') using a specific verb and resource, distinguishing it from sibling tools like faz_list_adoms by indicating it retrieves a single item. The additional sentence about empty ADOM adds relevant context without muddling the purpose.

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 establishes clear context: this tool fetches a single ADOM, and notes behavior when no ADOM is specified. It does not explicitly mention alternatives or exclude other tools, but the 'one' versus 'list' differentiation is implied by the verb and the sibling tool names.

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