sg_mrt_search

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

No annotations provided. Description mentions coverage (140+ stations, 6 lines) and 'FREE' cost hint. Lacks details on auth, read-only nature, pagination, or response structure.

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 concise sentences, front-loaded with key information. No wasted words.

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 simple search tool with 2 parameters and no output schema, description adequately explains return values (name, line codes, coordinates) and coverage. Sufficient for agent to invoke correctly.

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 both parameters with descriptions. Description adds value with partial match clarification, example values, and default limit. More helpful than schema alone.

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?

Clearly states 'Search MRT stations by name' with specific verb and resource. Returns station name, line codes, coordinates. Distinguishes from sibling sg_mrt_near which likely does proximity search.

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?

Implied usage for searching by name, but no explicit when/not to use or alternatives. No guidance on when to use sg_mrt_near instead.

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