editor-selection-get

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

With no annotations, the description must disclose behavioral traits. It states 'Get information' implying a read operation, but does not explicitly confirm non-destructiveness, permissions, or what happens when no selection exists. The minimal description leaves significant uncertainty about side effects.

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 two sentences, front-loading the purpose and succinctly referencing the sibling. Every word serves a purpose without waste.

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 the tool has six configurable boolean parameters and no output schema, the description is far too minimal. It does not mention what information is returned, how parameters affect the output, or any edge case handling (e.g., empty selection). This leaves the agent with insufficient context for correct usage.

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 description provides no information about the six boolean parameters. Schema description coverage is 0%, and the description does not explain what fields like 'includeGameObjects' or 'includeActiveObject' control. The agent cannot understand how to use these parameters based on the description alone.

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 clearly states the tool's action: 'Get information about the current Selection' and distinguishes it from the sibling 'editor-selection-set' by directing agents to use that tool for setting. This provides a specific verb and resource, effectively differentiating the tool.

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?

The description explicitly directs agents to use 'editor-selection-set' for setting the selection, offering clear context on when to use this getter versus the alternative. However, it does not provide exclusions or broader usage scenarios.

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