addGeoJsonPrimitive

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

Annotations already declare the operation is not read-only, not idempotent, and not destructive. The description adds the return shape and the large-dataset performance context, but does not disclose broader behavioral traits such as whether an existing layer with the same ID is replaced or whether rendering is asynchronous. With annotations available, this is adequate but not rich.

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 short sentences that front-load the core purpose and include the return contract. There is no filler or redundant elaboration.

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 rich parameter schema, annotations, and output schema, the description is nearly complete for guiding invocation. It could offer more detail on trade-offs versus addGeoJsonLayer or side effects, but the structured fields already cover most operational details.

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?

Schema description coverage is 100%, so each parameter is already well-documented in the schema. The description adds no additional parameter-level meaning beyond the general GeoJSON rendering context, which fits the baseline for high schema coverage.

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 identifies the action ('Render GeoJSON as Cesium primitives') and the intended use case ('large browser datasets'). It distinguishes itself from the sibling tool addGeoJsonLayer by emphasizing primitives and large-scale performance.

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 phrase 'for large browser datasets' provides clear context for when this tool is appropriate, implying a performance-oriented alternative to entity-based GeoJSON layers. It does not explicitly list exclusions or alternatives, but the usage context is strong enough to guide selection.

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