Read console logs

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

With no annotations present, the description carries the full burden and does so well: it discloses ordering (newest last), output-shaping behaviors (repeated lines collapsed to (xN), long messages truncated with full results saved to a greppable temp file), and error provenance tagging ('mcp:<line>' vs 'Opiumware:<line>'). These are non-obvious operational traits an agent could not infer from the schema.

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 core purpose leads in the first clause, followed by three tight bullet-style lines covering the debug loop, error tagging, and output shaping behavior. Every sentence carries information; there is no filler or repetition.

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 six-parameter tool with no annotations and no output schema, the description covers ordering, truncation, collapsing, and provenance tagging well enough to call it correctly. It stops short of describing the shape of individual returned entries, which is the only notable remaining gap.

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 the baseline is 3, but the description adds real meaning beyond it: it explains what sinceExecute actually captures (everything since that run started, including deferred errors and spawned loops) and frames grep as the way to filter the provenance tags. That is genuine added context on top of the schema's own 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?

States a specific verb and resource ('Read the Roblox client console') and scopes it precisely to print/warn/error from all scripts, including the game's own. This clearly separates it from siblings like network, status, and screenshot without the agent needing to open any schema.

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 gives explicit conditional guidance: call with sinceExecute=true after an execute run to catch deferred errors and spawned loops, or new=true for everything since the previous logs call. That is clear routing between parameter modes, though there is no explicit statement of when NOT to use this tool.

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