get_location_status

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

Annotations already provide safety (readOnlyHint, destructiveHint) and idempotency hints. The description adds 'live status' but no additional behavioral context like authorization, rate limits, or response details.

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?

One sentence, no wasted words, front-loaded with key information. Perfectly concise for a simple tool.

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?

Given the tool's simplicity (1 param, output schema exists) and rich annotations, the description is largely complete. It covers the what and how, though could mention rate limits or that output schema provides status details.

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 description coverage, the description adds meaning by clarifying that the 'location' parameter can be an id (integer) or exact name (string), which is not evident from the 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?

The description clearly states the action ('Get live status'), the resource ('for one system location'), and the method ('by id or exact name'). It distinguishes from siblings like 'get_location' and 'list_location_status' by specifying 'live status' and 'one'.

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?

The description implies when to use (when you have an id or exact name) but does not explicitly state when not to use or mention alternatives. No exclusions or comparative guidance provided.

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