addGeoJsonPrimitive

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

Annotations provide readOnlyHint=false and destructiveHint=false. Description adds performance trait, primitive rendering, and mutual exclusivity of data/url, which are not in annotations.

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?

Two sentences that immediately convey core purpose and key constraint. No wasted words, front-loaded with most critical information.

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?

Description is brief but covers main differentiator (performance, entity bypass). Lacks mention of return value (likely layer id), but given no output schema, this is acceptable. Schema covers parameter details. Minor gap on sessionId and allowPicking defaults, but not critical.

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 coverage is 100%, so each parameter has a description. Description adds no new parameter-level detail beyond the mutual exclusivity already noted in schema. Baseline score of 3.

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?

Clearly states it loads GeoJSON with high performance for large datasets, bypassing the Entity system. Distinguishes from addGeoJsonLayer which uses the entity system. Explicit verbs and resource.

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?

Implicitly indicates use for massive datasets needing performance, bypassing entity system. No explicit when-not or alternative names, but contrasting rendering approach provides context.

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