getSelectedTileFeature

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: the null-on-no-selection case and the snapshot-vs-dataset distinction. It does not mention session routing behavior when sessionId is omitted, which is the only remaining gap.

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?

Front-loaded with the core purpose and the follow-up action in the first two clauses, with no filler. The trailing return-shape sentence is somewhat redundant given a dedicated output schema exists.

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?

Covers the selection-null case, snapshot semantics, and the recommended follow-up tool, which is everything an agent needs to call this correctly. Return structure is also stated, though the output schema already covers it.

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?

Only one optional parameter (sessionId) with 100% schema coverage, so the schema already carries its meaning. The description adds nothing about multi-browser routing or the consequence of omitting sessionId; the baseline 3 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?

States a specific verb and resource: read the last clicked managed vector/3D Tiles feature attributes and layerId. It is clearly distinguishable from siblings like queryEntities or getEntityProperties because of the 'last clicked' selection semantics.

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?

Explicitly routes the agent: use updateLayerStyle with the returned layerId to style the feature. It also states the negative case (feature=null when nothing is selected) and the scope limit (metadata is a snapshot, not a whole-dataset query), which steers agents to queryEntities for dataset-wide lookups.

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