Ase Get Selection

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

No annotations are provided, so the description carries the full transparency burden. It only names a state without disclosing whether the call is read-only, what happens when no selection exists, or whether an active document is required.

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?

The description is very short and free of filler, which is positive. However, this reads as under-specification rather than effective conciseness: it lacks a verb and enough context to be self-sufficient.

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?

Because this is a zero-parameter getter with an output schema, the description does not need to explain return values, which mitigates the brevity. Still, edge cases like an empty selection and the active-document requirement are not addressed, leaving the definition merely adequate.

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 input schema has zero parameters and coverage is 100%, so there are no parameter semantics for the description to clarify. The zero-parameter baseline 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 a noun fragment ('Current selection state') that essentially restates the title 'Ase Get Selection'. It does not use a verb or specify what the agent will get (bounds, mask, etc.), so it does not stand alone as a clear action statement.

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 guidance on when to use this tool versus sibling tools like ase_get_pixels, ase_sprite_info, or the selection-manipulation tools. It also does not state any exclusions, prerequisites, or conditions that would make this the right choice.

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