threads_get_location

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

No annotations are supplied, so the description carries the burden; 'Get' implies a read but nothing states whether the call is side-effect free, what errors occur for a stale/unknown ID, or what fields the location object returns. For a low-risk single-resource read this is adequate but thin.

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, front-loaded with the action and resource, and the parenthetical ID-source hint follows immediately. No filler and nothing to trim.

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?

No output schema exists, so the description would ideally sketch what a location object contains (name, address, coordinates) so the agent knows what it can rely on. It also says nothing about missing/invalid ID behavior. Adequate for a lookup, but leaves the response shape entirely unstated.

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 coverage is 100%, so the baseline is 3, but the description adds genuinely useful semantics the schema lacks: where the location_id comes from (threads_search_locations or a post's location_id field). That provenance guidance helps the agent construct a valid value rather than guess.

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?

States a specific verb and resource ('Get a Threads location object by ID'), which is unambiguous and distinct from the sibling threads_search_locations that produces IDs rather than resolving them. Sibling differentiation is present via the explicit reference to the search tool as the ID source.

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?

Tells the agent when this is the right tool: after threads_search_locations, or when a post carries a location_id field. It stops short of stating when not to use it or what happens on an invalid ID, so it stops at clear context rather than full routing guidance.

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