connections_geocheck_by_node_result

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

No annotations exist, so the description carries the full burden. The 'GET' prefix hints at a read-only operation, but nothing is said about whether the job may still be running, whether polling is required, or what errors occur for an unknown jobId.

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 short, but the body is just the raw HTTP path plus a restated title, and the trailing 'Tags: Connections Controller' line is generator noise that consumes space without informing an agent.

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?

For a job-result retrieval tool with no output schema and no annotations, the description should at least sketch the returned geocheck payload or the job lifecycle; instead it leaves the agent with only an endpoint path.

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 required jobId parameter. The description only repeats the term 'Job ID' (already in the name), adding no format details, sourcing guidance, or distinction between job identifiers of different endpoint families.

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 phrasing 'Get Geocheck for Node by Job ID' names a verb and resource, but it largely restates the tool name and does not distinguish this result-fetching endpoint from its sibling connections_geocheck_by_node, with which an agent could easily confuse it.

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 is given: it doesn't say this retrieves the outcome of a previously-started geocheck job, nor when to prefer connections_geocheck_by_node or connections_connections_by_node_result instead.

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