getState

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

Explicitly states read-only and provides return format structure ({ status, message }), adding value beyond annotations. No contradictions.

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?

Very concise: three sentences serving distinct purposes (what, required param, return). Information is front-loaded and 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?

Covers all essential aspects for a simple get tool: action, input, output format. Lacks error handling or behavior when record not found, but sufficient for typical use.

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 0% schema coverage, description partially compensates by stating location_id is required and is a path parameter, and noting the primary key spelling. Lacks detailed semantic guidance on valid values or source.

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 the action (get/fetch), resource (state/province), and identifier (by location_id). Distinguishes from sibling tools like listStates (multiple) and getCity/getCountry.

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 clear context for fetching a single state row by location_id and specifies the required parameter. Does not explicitly list when not to use, but the purpose is self-explanatory given siblings.

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