xae_library_installed

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description usefully notes it returns every version of a library, but says nothing about the 500-item default cap, truncation behavior, or what plc_project_path changes.

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?

Two short sentences, front-loaded with what the tool returns before the filter detail. Slight awkwardness in the em-dash aside, but no filler.

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?

An output schema exists so return shapes need not be explained, and the tool is non-mutating. Still, two of three parameters and the result-cap behavior are unexplained, leaving an agent to guess the meaning of max_items and plc_project_path.

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 coverage is 0%, so the description must carry parameter meaning. It does explain the key one — name matches a partial name, any case — which the bare schema title does not, but max_items and plc_project_path are left completely undocumented in both places.

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 specific verb+resource: lists libraries installed in the repositories XAE uses, with the ScanLibraries reference and the fields returned (name, version, distributor). It is nearly distinguishable from xae_library_list/proj_libraries via 'installed in the repositories', but never names those siblings explicitly.

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 name-filter behavior is described, implying usage for lookups, but there is no explicit statement of when to use this versus xae_library_list, xae_library_repositories or proj_libraries. Usage must be inferred from the words 'installed' and 'repositories'.

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