trmnl_get_current_screen

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond annotations except the raw endpoint path — no note on which device the screen resolves to, whether it is cached, or what the call costs. Credit is minimal when the description only restates 'GET'.

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 short lines, front-loaded with the action, zero padding. The second line (the API route) is mildly redundant with the first but is cheap and does anchor the tool to a concrete endpoint.

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?

There is no output schema, so the description must carry the burden of telling the agent what comes back — instead it says only 'the current screen', which is undefined. Combined with the unresolved ambiguity against trmnl_get_display, an agent cannot confidently predict the result.

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 the single optional 'profile' parameter is documented in the schema ("Configured profile name; defaults to default"). The description adds no further meaning about how profile affects the returned screen, so baseline 3 applies.

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 ("Fetch the current screen") plus the underlying API route, so the basic intent is legible. However, it never says whose screen (device, user, profile) is returned, and with a sibling named trmnl_get_display — which sounds near-identical — no differentiation is offered. That leaves the agent guessing which of the two is the right call.

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?

There is no when-to-use guidance and no exclusion or alternative named. Given trmnl_get_display in the sibling list, the missing routing cue is a meaningful gap rather than a minor omission.

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