Read filed tickets' state

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

Beyond the annotations, it discloses the 5-minute-per-project read throttle, the stale-response behavior (fresh: false plus next read due), that only the tracker the server settings point at is read, credential sourcing from the environment, and that it sends nothing and touches no browser. This is exactly the operational context annotations alone cannot convey.

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 what and the throttling/freshness caveat are front-loaded, and every sentence carries substantive information. It is dense and the parameter guidance is appended after the behavioral notes, which is slightly less efficient but still well organized.

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?

An output schema exists, so return values need not be spelled out, and the description still covers freshness, caching, tracker selection, and auth. Nothing an agent needs to invoke it correctly is missing.

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 schema coverage at 100% and a single parameter, the schema already documents address. The description restates the same condition ('when no check is open in this conversation, pass the site's address') without adding format or sourcing detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (list) and resource (tickets filed by this project) plus what the return contains: tracker open state and whether the problem is still open. It names the sibling that files tickets (scout_ticket_file / export), so an agent can distinguish reading status from creating tickets.

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?

Gives a clear context for use (checking whether filed tickets/problems are still open) and an explicit conditional for the single parameter: pass the site address when no check is open in this conversation. It does not explicitly contrast with scout_tickets or scout_ticket_preview, so alternatives are only implicit.

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