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

Annotations already declare the safe read-only profile, so the bar is lower, and the description still adds real behavioral context: the 20 auto-publishes per project per day cap, the fact that drafting triggers an immediate auto-publish, and that calls consume no credits.

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?

One dense sentence plus a short qualifier; the scope (which issue types are auto-published) is front-loaded and every clause adds information. The opening 'Patches:' fragment is slightly telegraphic but still efficient.

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 single-parameter, read-only list tool with no output schema, the description conveys what each entry represents (an issue type auto-published on draft) plus the rate cap and cost, and annotations cover safety. Only the exact return shape is left unspecified.

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% with a single required projectId documented in the schema (including how to obtain it), so the description rightly does not repeat parameter details. Baseline 3 applies since the schema carries full parameter semantics.

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 exactly which resource is returned: every issue type the project auto-publishes AI-drafted patches for. Combined with the name, the verb+resource pair is unambiguous, though it does not explicitly contrast itself with sibling list_patches or enable/disable_patch_auto_publish.

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?

There is no explicit when-to-use guidance or mention of alternatives such as enable_patch_auto_publish/disable_patch_auto_publish, which manage the very rules this tool reads. The 'FREE (no credits), read-only' note hints at cost considerations but is not usage direction.

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