aiworkhub_task_audit_log_read

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

With no annotations, the description explicitly carries the safety profile: read-only, never writes, never enables writes, never launches processes, authority flags preserved false. That is the key behavioral disclosure for a mutation-averse agent, though it omits ordering, pagination, or truncation semantics for the returned entries.

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?

Four short lines, front-loaded with the read-only guarantee, and no filler. The repeated 'never ...' clauses are slightly redundant but each reinforces a distinct non-action.

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 shape need not be described, and the description still sketches the counts/entries payload. For a one-optional-param read tool the remaining gap (default and cap for max_entries) is minor.

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 the single optional parameter max_entries is undocumented in the schema. The description partially compensates by saying it returns 'the last N audit entries', which maps N to max_entries, but gives no default, bounds, or ordering rule.

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?

Specific verb and resource: 'inspect write-gate audit log summaries', plus what comes back (counts by tool/action and last N entries). It is clear on its own, but does not distinguish itself from adjacent audit-summary siblings such as aiworkhub_launch_queue_audit_summary_readonly or aiworkhub_cli_adapter_audit_summary_readonly.

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?

No statement of when to call this versus other audit/telemetry tools, and no prerequisites or exclusions. The 'write-gate' qualifier hints at domain but leaves the routing decision to inference.

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