Singapore Location Intelligence MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'real-time' and 'comprehensive' but doesn't specify data freshness, rate limits, authentication requirements, error conditions, or what 'travel impact analysis' entails. The description is insufficient for a tool with multiple parameters and no output schema.

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, efficient sentence that front-loads the core purpose. Every word earns its place - 'comprehensive real-time weather conditions,' 'Singapore,' and 'travel impact analysis and advisories' all provide valuable context without 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?

For a tool with 5 parameters, nested objects, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, how 'travel impact analysis' manifests in outputs, or provide behavioral context needed for proper invocation. The description assumes too much given the complexity.

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 100%, so the schema already documents all parameters thoroughly. The description doesn't add meaningful parameter semantics beyond what's in the schema - it mentions 'travel impact analysis' which might relate to 'includeAdvisories', but this is already clear from the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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's purpose: 'Get comprehensive real-time weather conditions for Singapore with travel impact analysis and advisories.' It specifies the action ('Get'), resource ('weather conditions'), and scope ('Singapore'), but doesn't explicitly differentiate from sibling 'get_weather_advisory' which might overlap in functionality.

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?

No guidance is provided about when to use this tool versus alternatives like 'get_weather_advisory' or other weather-related tools. The description mentions travel impact analysis but doesn't explain when this is preferable to basic weather data or other siblings.

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