aiworkhub_dashboard_kb

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

Annotations already declare readOnlyHint=true, so the safety profile is known; the description still adds useful context that it opens the KB SQLite store read-only, does not mutate entries, and does not bump usage counters, plus that only canonical entries are listed. This is genuine added signal, though the read-only nature is restated three times.

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?

Only three sentences and the resource scope is front-loaded before the alternative routing. Minor waste from repeating 'READ-ONLY' in the prefix and again as 'read-only mode without mutating entries or usage counters'.

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 one-parameter, read-only list tool with an output schema and clear annotations, the description covers purpose, ordering ('newest'), scope (active repository), canonical filtering, and alternatives. Nothing an agent needs to invoke it correctly is missing.

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 100% and the single 'limit' parameter is documented in-schema with its default and 1..500 clamp. The description adds nothing about parameters, so baseline 3 applies despite the otherwise strong narrative.

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 (list), resource (newest canonical Knowledge Base entries) and scope (active repository). It also explicitly distinguishes itself from aiworkhub_dashboard_memory and aiworkhub_dashboard_sessions, so an agent can route correctly without opening sibling schemas.

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?

Explicitly says 'Use this to browse repository Knowledge Base articles, categories, and tags' and names two alternatives with the condition that selects each. The when-to-use mapping is complete for the dashboard KB read case.

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