get_logs

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

Annotations already declare readOnlyHint=true, so no mutation. The description adds behavioral context: events are ordered newest last, the buffer composition includes server and browser events, and incremental tailing is supported via sinceSeq. It doesn't discuss rate limits or exact return format, but adds value beyond 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 two sentences: the first states the core purpose and ordering, the second covers filtering, scoping, and alternatives. It is concise, front-loaded, and every sentence adds value without redundancy.

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?

Given the tool has 6 parameters, no output schema, and is a log retrieval tool, the description covers the main use cases, filtering options, and differentiation from siblings. It does not detail the return format, but the schema descriptions and the term 'events' provide adequate context for an agent.

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 coverage is 100%, so baseline is 3. The description adds context like 'Scope to one project's logs with `app`' and explains the purpose of filtering parameters (source, stream, grep) and incremental tailing (sinceSeq). This provides meaning beyond the individual schema descriptions.

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 returns recent events from a unified buffer (server stdout/stderr + browser console/network/pageerror) with newest last ordering. It distinguishes from siblings 'get_logs_around' and 'diagnose' by mentioning their specific use cases.

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 explicit guidance on when to use this tool: for filtering by source, stream, grep, and incremental tailing with sinceSeq, and scoping to a project. It also clearly states when to use alternatives: 'For events around a specific moment use get_logs_around; to triage errors first use diagnose.'

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