connections_geocheck_result

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. Beyond that the description adds nothing: for a job-result tool the critical behaviors are whether the job may still be pending, whether results expire, or whether the call blocks, and none of these are disclosed.

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?

A single short, front-loaded sentence with no filler. It is efficient, though the brevity is partly under-specification rather than tight editing.

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, no annotations beyond readOnly, and no parameter documentation in the schema. For a tool whose entire value is retrieving the outcome of a prior request, the definition omits the request/result relationship and the state of the returned result, leaving the agent to guess at the workflow.

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 description coverage is 0% for the single jobId parameter, so the schema gives no type/format/source context. The description does add real meaning by tying jobId to a Job (implying it comes from the request call), but it stops short of naming the source tool or the ID format.

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 verb ('Get') and a resource ('Geocheck for Node') qualified by 'Job ID', which is more than a tautology. But 'Geocheck' is unexplained jargon and the description never signals that this is the result-fetching half of an async pair with connections_geocheck_request, so an agent cannot cleanly distinguish it from that sibling.

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?

No when-to-use guidance at all. There is no mention of the connections_geocheck_request tool that presumably creates the job, nor of when the result is ready, so the agent must infer the two-step flow entirely from naming conventions.

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