Help and Tool Discovery

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

No annotations are provided, so the description carries the behavioral burden. It discloses that listing is badge-filtered and that category reassignment is for a session, adding useful context beyond the schema. It doesn't detail all side effects, but the session-scoped wording covers the main mutation concern.

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 compact: a one-sentence purpose statement followed by explicit use/when-not conditions. Every sentence earns its place, and the core behavior is front-loaded.

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 help/discovery tool with no required parameters and no output schema, the description plus 100% schema coverage is complete: it covers both actions, keyword search behavior, session-scoped category reassignment, and the boundary with badge_briefing. Nothing essential 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 description coverage is 100%, so every parameter is already documented. The description's 'find by keyword' and 'override a tool's category' map loosely to the query and action/category/tool_name parameters but add no new details; the baseline of 3 applies because the schema does the heavy lifting.

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 states a specific verb and resource: 'Show the available tools grouped by category (badge-filtered) or reassign a tool's category.' It names two distinct actions and distinguishes itself from the badge_briefing prompt, so an agent knows what this tool does and is not.

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?

It provides explicit 'Use when' conditions (discover tools, find by keyword, override category) and a 'Do NOT use when' exclusion with a named alternative (badge_briefing prompt). No inference is required.

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