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

Annotations already declare readOnlyHint=true, and the description reinforces with 'Read-only.' It adds that this is the owner's triage queue and the workflow note about checking before proposing, which are useful cues beyond structured data, but it doesn't describe filtering, ordering, or behavior with project_id.

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 description is extremely brief and front-loaded: 'PENDING Inbox' conveys the core immediately. Every word serves a purpose, and the usage guidance is packed into two short clauses.

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 simple read-only tool with one optional parameter, it covers purpose and usage context well. However, the lack of parameter semantics and any hint about the returned data (e.g., a list of pending items) leaves ambiguity. It's adequate but not fully complete.

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?

The input schema has a single optional project_id with 0% description coverage, and the tool description does not mention it at all. An agent cannot know whether project_id scopes the inbox or is ignored, making the parameter semantics completely unexplained.

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 clearly identifies the tool as the owner's pending inbox/triage queue, implying it retrieves pending items. It distinguishes itself from proposal-related siblings by framing it as a pre-proposal check, though it doesn't explicitly state the return format.

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 explicitly instructs to 'Check BEFORE proposing — avoid duplicates,' giving a clear when-to-use directive. It doesn't mention alternatives or exclusions, but the context strongly implies this is a prerequisite before proposing.

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