audit_issue_list

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safe read-only nature is covered. The description adds that the tool returns status, assignee, and last update, but this is more about output content than behavior (e.g., no mention of pagination, rate limits, or error handling). It does not contradict annotations, so a 3 is appropriate.

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 succinct and well-structured: first line states the function, second line gives the use case, and then an Args block clarifies parameters. Every sentence earns its place, and the most important information 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?

With an output schema present (though not shown) and rich annotations covering safety, the description provides enough information to call the tool correctly for a simple read operation. It could mention limitations or batch size, but it is effectively complete for the intended use case.

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?

Although the schema description coverage is 0%, the description explicitly explains both parameters: issue_ids format (comma-separated IDs/URLs with an example) and instance optionality. This adds meaningful meaning beyond the raw schema, compensating for the lack of schema-level descriptions. Minor gap: no details on default instance behavior.

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: getting current status, assignee, and last update for a list of issues. This is a specific verb and resource, and the use case 'validating a list' adds context. However, it does not explicitly differentiate from siblings like get_issues or search_issues, though the focus on auditing is distinct enough.

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 provides a clear context for when to use this tool ('validating a list against current state'), which helps an agent understand the intended scenario. It does not mention alternatives or exclusions, but the purpose is clear enough to guide selection among siblings.

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