list_options

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

Annotations already declare the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description only needs incremental context. It adds that the catalog is versioned and what attributes are inspectable, but says nothing about pagination behavior despite limit/offset parameters, which is a trait annotations do not cover.

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?

A single front-loaded sentence with no filler; the verb and resource lead and the semicolon-clause adds the payload summary. Efficient, though the second clause is packed and could have traded some attribute listing for usage 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 four-parameter search tool with no output schema and no annotation coverage of result shape, the description omits how query matches, how results are paged, and how scope narrows the catalog. An agent can guess the intent but not call it correctly on the first try.

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 0%, so all four parameters (limit, query, scope, offset) are undocumented in both structured fields and the description. The only faint hint is the word 'scopes' in the list of attributes, but query semantics, default vs max limit, and offset paging are entirely unaddressed.

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?

States a clear verb (Search) plus resource (versioned FFF configuration catalog) and enumerates what the results expose (types, units, ranges, defaults, scopes). That distinguishes it from get_settings/list_profiles, though it never names a sibling explicitly and 'FFF' is unexplained jargon.

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?

There is no guidance on when to call this versus get_settings, get_environment, or list_profiles. The word 'Search' implies a lookup intent, but the description never states the condition that selects this tool over its catalog-reading siblings.

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