aiworkhub_quality_profile

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

The readOnlyHint annotation already declares the safety profile, so 'READ-ONLY' in the description is redundant. 'Zero-config' adds a small amount of context, but the description gives no deeper behavioral detail such as data sources, scope, or what the zero-config detection actually covers.

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 definition is short and front-loads the READ-ONLY constraint, which is efficient. However, the compressed phrase 'detected languages/declared/installed tools' is under-structured and reads more like notes than a clear tool summary.

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?

Although the tool is low-complexity, has an output schema, and carries a readOnlyHint, the description still leaves the core purpose ambiguous. An agent cannot confidently tell what a 'quality profile' is or why it would call this tool instead of the many sibling quality/profile tools.

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 tool has zero parameters, so there is no parameter documentation gap for the description to fill. The empty schema is self-explanatory and the description does not need to explain parameters.

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 is a cryptic fragment: 'READ-ONLY: zero-config detected languages/declared/installed tools.' It hints at a profile of detected languages and tools but never states a clear verb or what a 'quality profile' actually returns. It also does not distinguish this tool from nearby profile/quality siblings such as aiworkhub_suite_profile or aiworkhub_quality_run_checks.

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 when-to-use guidance, no prerequisites, and no alternatives named. The 'READ-ONLY' prefix signals a safe read operation, but nothing tells an agent when to choose this over other profile or quality tools.

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