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

The description adds functional behavioral context by stating that 'deliveryFeed' honors existing system settings (PAT/project) as a fallback if the argument is not specified. This adds operational behavior beyond what is present in the schema or 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 two sentences are highly efficient. The first establishes the scope, and the second front-loads critical operational logic regarding the arguments.

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?

The definition is complete. It clearly defines the scope (organizational, recent), the primary use case, and the specific operational fallback logic for key inputs, which is sufficient for a read-only monitoring tool.

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?

With 100% schema description coverage, the description provides little specific meaning regarding the parameters. It merely reinforces the `deliveryFeed` argument's behavior as a default.

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 immediately defines the tool's purpose: to retrieve the most recent occurrences across the organization. It explicitly identifies its use case for live monitoring and testing workflows.

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?

While it states when the tool is 'useful' (for live monitoring), it does not provide explicit guidance on when it should or should not be used in relation to other available bug or event tools.

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