Ler o console do FiveM

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

With no annotations, the description carries the behavioral disclosure burden. It adds relevant context by saying the lines are 'capturadas por esta sessão' and that the tool is for post-command output or error investigation, but it does not disclose whether reading consumes or clears the buffer, nor how far back the captured lines go.

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?

Two sentences deliver purpose, optional filter, and usage guidance with no filler. It is front-loaded with the core behavior ('Últimas linhas do console...') before the usage note.

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 low-complexity read-only tool, the description adequately covers what it returns, the optional filter, and the intended usage scenarios. It lacks an explicit note about output formatting or persistence, but the schema and session qualifier make the tool actionable.

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 description coverage is 100% and both parameters are already documented with descriptions. The tool description adds only that the regex filter is optional, which is marginal value beyond what the schema already provides.

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 that the tool returns the latest server console lines captured in the current session, with an optional regex filter. The resource ('console do servidor') and the session-scope qualifier distinguish it from sibling tools like fivem_status and fivem_players. The title adds the explicit verb 'Ler'.

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 usage guidance: use it after a command that keeps printing, or to investigate errors. It does not, however, name alternatives or state when not to use the tool, so it stops short of full routing guidance.

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