daily

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

The description indicates a read-only operation (fetch, enrich, return), but the annotation readOnlyHint=false contradicts this, suggesting possible mutations. No side effects are mentioned, and destructiveHint=false adds no clarity. This is a clear contradiction between description and annotations.

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, clear sentence with no extraneous information. Every part is necessary to convey the tool's purpose and behavior.

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?

While the description explains the main actions, it does not specify the scope (e.g., which repository), the return format in detail, or whether it performs any side effects (e.g., notifications). The missing output schema and the contradiction with annotations reduce completeness.

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 no parameters, so schema coverage is 100% trivially. The description adds value by explaining what the tool does overall, serving as the baseline for parameterless tools.

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 runs a daily PR monitoring check, specifying actions: fetch all open PRs, enrich with CI status, reviews, and conflicts, then return a prioritized summary. This distinctly differentiates it from siblings like claim, dismiss, or read.

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 no guidance on when to use this tool versus alternatives such as `read` or `search`. It only states it is a 'daily' check, implying periodic use, but lacks explicit context, exclusions, or alternatives.

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