Iniciar o PJe-Calc

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

Goes beyond the annotations (idempotentHint, destructiveHint=false) by disclosing the up-to-3-minute wait, that Tomcat is started as the official launcher, that no window/browser opens in headless mode, and the resulting port/URL. It does not state what happens if the service is already up or what a failure looks like.

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?

Front-loaded with the action and its timeout, then the mode semantics, then the follow-up URL. Dense and mostly waste-free; the trailing localhost sentence is marginally useful but slightly beyond the tool's own scope.

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?

No output schema and a single optional parameter, so the description carries the burden and does so adequately: what starts, how long it waits, the modes, and the endpoint exposed. It omits how to confirm readiness afterward (pjecalc_status) and the return shape.

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% (baseline 3), but the description adds real meaning to the enum values — "sem-navegador" is explained as launching Tomcat without a window, "normal" as equivalent to iniciarPjeCalc.bat — which the terse schema text does not convey.

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 ("Inicia o PJe-Calc") and disambiguates the two launch modes with concrete behavior for each. It does not, however, distinguish itself from nearby siblings like pjecalc_abrir_interface or pjecalc_status, which an agent must sort out on its own.

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?

"sem-navegador (padrão) ... ideal para o agente" gives clear guidance for choosing a mode, but there is no guidance on when to pick this tool over the sibling launch/status/info tools, nor any stated prerequisites (e.g. is the app already running?).

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