GetSelectedElements

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it doesn't say whether an empty selection returns an empty list or an error, nor what element representation is returned. With annotations carrying the burden, a 2 is warranted for a description that contributes no extra behavioral context.

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?

One front-loaded sentence that states the resource and scope. The trailing parenthetical '(Tapir, Element Commands)' is grouping metadata rather than useful agent-facing content, which keeps it from a 5.

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?

For a zero-parameter read-only tool with no output schema, the description conveys the essential contract: it returns the list of selected elements. It could say more about the returned element shape or the empty-selection case, but the core is complete.

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 disambiguate; baseline for 0 params is 4. Schema coverage is 100% with an empty parameter object, leaving no gaps.

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+resource ('Gets the list of the currently selected elements'), and the qualifier 'currently selected' distinguishes it from GetAllElements, GetElementsByType, and FilterElements. It does not explicitly name those siblings, so it stops short of a 5.

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?

Usage is implied by the name and description: call it when you need the user's current selection. There is no explicit when-to-use guidance, no note that the selection may be empty, and no routing to related tools like ChangeSelectionOfElements or HighlightElements.

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