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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds that results carry RBAC context (identity, role, required permission, eligibility), but this is largely restating what the output schema already conveys and says nothing about ordering, volume, or staleness of pending items.

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?

Two tight sentences: the capability and its returned context first, the use case second. No filler, everything 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?

An output schema and rich annotations carry most of the load, so the description needn't explain returns. However, with both parameters undocumented in the schema, the description should have clarified valid status values and category semantics; it does not.

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 0%: 'status' and 'category' have only titles and defaults. The description mentions 'pending' items, hinting at the status default, but never explains what other status values exist or what categories mean/filter, leaving the agent to guess at the one meaningful filter parameter.

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 (fetch pending HITL approval items) plus the RBAC payload it returns, so the agent knows exactly what this tool provides. No sibling tool covers HITL approvals, so explicit differentiation isn't needed, but the description doesn't say so.

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?

"Use this to check what needs human approval before proceeding" gives a clear triggering context and even implies workflow placement. It stops short of naming when not to use it or pointing to any alternative path for already-approved/denied items.

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