Connect GeoJSON feature bus

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

Annotations indicate readOnlyHint=false and openWorldHint=true, but the description only says 'Create a scaffold' without additional behavioral context. It does not explain side effects, external connections, overwrite behavior, or anything beyond what annotations already imply, adding little transparency.

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, front-loaded sentence with no filler. It communicates the core purpose and key deliverables efficiently, every phrase adds value.

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 10 parameters, no output schema, and minimal annotations, the description lacks essential context such as prerequisites, post-conditions, or what the scaffold is used for. It does not explain the 'connect' aspect of the tool name or the impact of the openWorldHint, leaving the operation contextually incomplete.

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 only 20% (name and parent_path have descriptions), leaving 8 parameters undocumented. The description lists high-level components like 'feature rows, property maps, style rules' but does not map these to specific parameters or explain defaults, enums, or relationships, so it fails to compensate for the low 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 uses a specific verb 'Create' and names the resource 'GeoJSON feature scaffold' with enumerated components (feature rows, property maps, style rules, adapter source, projection/privacy notes). This distinguishes it from most siblings, though the tool name says 'connect' while description says 'create', causing slight ambiguity.

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. With a large sibling list including many 'connect_*' and 'create_*' tools, there is no mention of preferred scenarios, exclusions, or alternative tools.

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