pixera_refresh_mapping

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

With no annotations, the description carries the full burden, and it discloses nothing about side effects, idempotency, whether the refresh is synchronous or asynchronous, or what permissions are needed. For a trigger/mutation-style operation this is a meaningful gap, though the presence of an output schema partially limits how much return-value detail is needed.

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?

A single front-loaded sentence with no wasted words, but its brevity borders on under-specification rather than efficient conciseness.

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?

Given a mutation-style trigger with no annotations and an undocumented parameter, the description is too thin; only the return-value aspect is covered by the output schema. An agent cannot tell when the refresh is needed, what it affects, or whether it blocks.

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?

There is one required parameter (screen_name) with 0% schema description coverage, and the description adds nothing about naming, format, or whether the screen must already exist. The description fails to compensate for the documentation gap.

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 pairs a specific verb ('Trigger') with a specific resource ('a mapping refresh on a screen'), so an agent knows the action and target. It doesn't differentiate itself from siblings like pixera_export_mappings or pixera_import_mappings, but the operation is distinct enough from the rest of the list.

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?

No when-to-use, prerequisite, or alternative guidance is given. The agent must infer that this should be invoked after mapping changes, and nothing indicates whether it is safe to call repeatedly or when it is required.

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