aiworkhub_suite_profile

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

With no annotations present, the description carries the full burden, and it discloses only one trait: 'shell is never used.' It does not say whether the run is read-only, whether it mutates repo state, whether it is sandboxed or what permissions are required, which is thin for an execution tool.

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 key behavior (one check, repeated) comes first and the shell note is appended efficiently. It is terse rather than padded.

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 values need not be explained, but with zero annotations, zero parameter documentation and no usage context, an agent cannot reliably determine when or how to call this. The definition omits more than it conveys for a tool of this complexity.

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% and neither parameter is named in the description. 'one repo-declared quality check' faintly hints that check_id names a declared check, and 'repeatedly' faintly hints at repeats, but there is no explanation of the default of 2, accepted values, or format, so the gap is essentially 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 specific verb and resource: 'Execute one repo-declared quality check repeatedly,' which pins down scope (single check, repeated) beyond a bare name. However, it does not distinguish itself from close siblings like aiworkhub_quality_run_checks, aiworkhub_quality_profile, or aiworkhub_quality_run_checks, leaving an agent to guess which quality-family tool to pick.

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 and no mention of alternatives, despite a large quality/check family among the siblings. The adverb 'repeatedly' and the 'repo-declared' qualifier imply context but never state the condition that selects this tool over aiworkhub_quality_run_checks.

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