pilot_geolocation

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

No annotations, so description carries full burden. Discloses simulation, clear option, and accuracy default. However, lacks details on persistence, page-specific effects, or HTTPS requirement beyond a brief error mention.

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?

Description is well-structured with sections (purpose, parameters, returns, errors). Every sentence adds value; no fluff or redundancy.

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?

No output schema, but return behavior is described as confirmation. Errors are listed. The tool is simple, so completeness is high, though could mention whether location is overridden per session or permanently.

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 covers all 4 params with descriptions. Description adds examples for latitude/longitude, clarifies default for accuracy, and explains clear behavior, providing significant added value.

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?

Description clearly states verb 'Set or clear browser's reported GPS coordinates' with specific resource (geolocation). It distinguishes from siblings as no other tool simulates location.

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?

Provides explicit use cases (testing location-aware apps, simulating different locations). Lacks explicit when-not-to-use or alternatives, but errors give some guidance (e.g., navigate first).

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