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

With no annotations provided, the description carries the full burden. It discloses the authentication requirement and implies user-specific filtering. However, it does not mention read-only behavior, error handling, or return format. The user_email schema description adds a security default, but that's outside the main description.

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 a single, front-loaded sentence that states the purpose and authentication requirement without filler. The bilingual repetition (Chinese and English) is slightly redundant but serves a multilingual audience and is not excessive.

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?

This is a simple list tool but has 4 parameters, no annotations, and no output schema. The description covers only purpose and authentication, leaving url and limit unexplained and failing to describe return values or pagination behavior. It is insufficient for a 4-parameter tool with no structured support.

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 50% (user_email and session_token have descriptions, but url and limit do not). The main description repeats the requirement for user_email and session_token but adds no new meaning, and it fails to compensate for the undocumented url and limit parameters.

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 states the tool's function: 'List a user's bug reports' with a specific verb and resource. It also specifies the authentication requirement. However, it does not explicitly differentiate from sibling tools like get_report_overview, though 'bug reports' is distinct from the log-related siblings.

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?

The description notes that user_email and session_token are required for identity verification, which is a clear precondition. However, it provides no guidance on when to use this tool over alternatives (e.g., get_report_overview) and lacks any exclusions or 'when not to use' statements.

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