get_selection

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the scope ('currently selected') and implies a read-only operation, but does not describe the return format, behavior when nothing is selected, or whether order/presence is guaranteed. This is acceptable for a simple getter but lacks depth.

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 a single, short sentence ('Get all currently selected objects') with no redundant or extraneous content. Every word contributes to the meaning, making it extremely concise and well-structured.

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 zero parameters and no annotations or output schema, the description is the sole source of context. It clearly identifies the resource but does not specify the return type (e.g., object IDs, references) or edge-case behavior, making it minimally adequate but not fully complete for an agent.

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 has zero parameters, so the input schema is empty and schema_description_coverage is 100%. The description adds no parameter details because none exist; the baseline of 4 applies since there is no parameter information to convey.

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 'Get all currently selected objects' uses a specific verb ('Get') and resource ('currently selected objects'), clearly conveying the tool's function. It is distinct from siblings like set_selection, but does not explicitly differentiate itself by naming alternatives or contrasting with other getters.

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 provides no guidance on when to use this tool versus alternatives such as search_objects or get_attributes. There is no mention of use cases, prerequisites, or exclusions, leaving the agent to infer usage solely from the phrase 'currently selected objects'.

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