singapore_query_recycling_rates

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

Annotations already establish that this is a read-only, idempotent, non-destructive query. The description adds that results return bundled source coverage and advises fetching metadata for current coverage, but it does not add much else about rate limits, permissions, or result behavior.

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 front-loaded with the core purpose and follows with practical query guidance. It is generally efficient, though the coverage and metadata sentence is slightly incidental.

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 read-only dataset query tool with six parameters, an output schema, and annotations, the description supplies enough context to call it correctly: what it queries, which dataset to inspect, and what query modes are supported. Minor gaps remain around sibling selection and exact return behavior.

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?

With 50% schema description coverage, the description usefully enumerates the main parameter capabilities: exact filters, column text search, fields, sort, and pagination. It does not explain syntax in depth, but that is largely left to the schema descriptions for q, filters, and sort.

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 states a specific verb and resource: query recycling rates by waste type, attributed to Singapore's National Environment Agency. It also names the exact dataset ID to inspect, which makes the intent clear even without explicit sibling comparison.

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?

It gives a clear usage context and prerequisite: inspect the named dataset first for filter fields. It also lists supported query capabilities, though it does not explicitly exclude or compare against sibling tools such as the generic query_dataset.

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