astrax_info_pantalla

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

With no annotations, the description carries the full burden. It discloses the return content (pixel dimensions, top-left origin) and that the value is effectively constant (call once), which is helpful. It does not state that the call is side-effect free or mention any auth, but for a trivial info tool the gap is minor.

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 compact clauses with the return value front-loaded and no filler. Appropriately sized for a one-liner info tool.

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 the description need not detail return values. For a zero-param, read-only info tool with no annotations, purpose plus the call-once hint covers what an agent needs; only an explicit read-only/no-side-effects statement 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?

The tool takes zero parameters, so the baseline of 4 applies. There is no parameter syntax the description needs to explain beyond what an empty schema already communicates.

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 states a specific resource and what it returns: the screen size in pixels, with the coordinate origin specified (top-left). This is clearly distinct from screenshot/view siblings, though it does not name them explicitly.

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?

"Llámala una vez" gives a useful caching hint (fetch once and reuse), which is genuine guidance. However there is no statement of when to use this versus siblings like astrax_capturar_pantalla or astrax_ver_pantalla; usage context is only implied.

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