mouseGetCursor

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the genuinely useful precondition that a trusted owner and an interactive desktop session are required, but says nothing about the returned value or failure behavior when the desktop is not interactive.

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 sentences with the environment constraint front-loaded and no filler. The only wasted token is the 'Windows AutoIt mouseGetCursor' prefix, which duplicates the name instead of describing behavior.

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?

With no output schema, the description carries the burden of explaining the return value, and it does not — an agent cannot tell whether this yields a cursor ID, a shape enum, or coordinates. The prerequisite is disclosed, but the essential output contract 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 there is nothing for the description to clarify beyond what the empty schema shows; the baseline for a parameterless tool 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?

The description is essentially the tool name restated with a platform prefix ('Windows AutoIt mouseGetCursor') and never says what the tool actually retrieves — the current cursor shape/handle/ID. It also fails to distinguish it from the sibling mouseGetPos, which an agent could easily confuse it with.

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 statement of when to call this versus alternatives such as mouseGetPos or takeScreenshot. The only guidance is an environmental prerequisite (trusted owner, interactive Windows x64 desktop), which is context rather than usage direction.

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