Connect GPS fleet tracker

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

Annotations already declare the tool as write-oriented (readOnlyHint=false), non-destructive, and open-world. The description adds context by listing the scaffold's contents (privacy policy, credential notes, geofence maps), which clarifies what the side effects create. It does not contradict annotations and provides useful artifact-level detail.

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 sentence that front-loads the primary verb and resource ('Create a GPS/fleet tracking scaffold'). The enumeration of contents is somewhat dense but each phrase is meaningful. It is appropriately sized without redundant wording.

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?

For a scaffold tool with 10 parameters and no output schema, the description gives a high-level overview but leaves key questions unanswered: what exactly are 'sanitized asset rows'? What does 'adapter source' entail? What are the prerequisites or side effects on the project? Annotations cover the safety profile, but the description could provide more operational context.

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%, with only name and parent_path described. The tool description does not explain most parameters (provider, adapter_mode, geofence_count, update_rate_hz, tracked_asset_count, adapter_url, fleet_label, active). It offers only implicit hints like 'geofence maps' for geofence_count and 'adapter source' for adapter_url/adapter_mode, which is insufficient for a 10-parameter tool with 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 clearly states the tool creates a GPS/fleet tracking scaffold and enumerates its components (sanitized asset rows, geofence maps, privacy policy, adapter source, credential/privacy notes). The verb 'Create' and specific resource distinguish it from sibling integration tools like connect_blackmagic_atem or create_blacktrax_tracking_bus.

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 implies usage when a GPS fleet tracking scaffold is needed, but it does not explicitly state when to use this tool over alternatives or mention any exclusions. No sibling comparisons or conditionals are provided.

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