sg_nearby

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

With no annotations, the description discloses authentication requirements, a behavioral trait. However, it does not describe output format, error handling, or whether the operation is read-only, though 'Find' implies reading. The disclosure of required credentials adds value beyond the schema, but overall behavioral transparency is limited.

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 efficient sentences: one for purpose and auth, one for theme examples. No redundant phrases, front-loaded with the core action, and every clause adds useful 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?

The tool is simple (3 params, no output schema), but with no annotations the description needs to cover more. It handles prerequisites and themes, but omits what the response will contain or how results are ordered. Given low complexity, it is minimally complete but leaves the output unaddressed.

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 33% (just the 'theme' parameter). The description enriches theme semantics with common examples, but gives no additional info for latitude/longitude beyond the word 'nearby'. Since these are standard coordinate params, the lack is partly compensated by their natural clarity, but the description could specify units or ranges.

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 ('Find') and resource ('nearby amenities using OneMap themes'), making the tool's purpose clear. It does not explicitly differentiate from siblings like sg_hawker_centres, but the 'OneMap themes' qualifier and theme examples provide functional distinction.

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?

States a clear prerequisite ('Requires SG_ONEMAP_EMAIL + SG_ONEMAP_PASSWORD') and provides common theme examples, which guides selection. It does not explicitly mention when not to use it, but the examples and purpose imply suitable scenarios, so it's clear context without exclusions.

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