qobrix_get_project_coordinates

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

With no annotations provided, the description carries the full burden. It conveys that the tool is a read operation ('Get') and mentions optional filtering, but it does not disclose whether the response contains multiple projects, pagination behavior, or any other side effects. It is not misleading, but it lacks depth.

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 two short, focused sentences. The main action is front-loaded, and each clause adds value: specifying the coordinates and their use case, followed by the optional filter capability. No waste.

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 simple tool with one optional parameter and no output schema, the description adequately states the purpose and filter option. However, it does not explain the return format or behavior when no filter is provided (e.g., returns all projects). The schema covers search syntax, but the description leaves minor gaps.

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?

The schema description coverage is 100% for the only parameter 'search', providing comprehensive details on the DSL. The tool description adds minimal value by noting the filter is optional, which is already implied by zero required parameters. Baseline of 3 applies.

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 it gets lat/lng coordinates for projects, with a specific verb and resource. It distinguishes itself from siblings like qobrix_get_property_coordinates by explicitly targeting projects, and from qobrix_get_project by focusing on coordinates.

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 provides a use case ('useful for map display') and mentions optional filtering, but it does not explicitly state when to use this tool versus alternatives such as qobrix_get_property_coordinates or qobrix_search_projects. No exclusions or alternative tool names are given.

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