f360_ping

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

With no annotations present, the description carries the burden and does disclose the key behavior: it is a read-only responsiveness probe and it returns connectivity status, version, and active-design state. It leaves out whether failures surface as errors vs. a status value, and any timeout behavior.

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?

Three short sentences with zero waste. Purpose comes first, return values second, and the routing directive ('use this first') lands last where an agent will act on it.

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 must describe return values – and it does, naming status, version, and design-open state. Error or failure-signaling semantics are the one remaining gap for a diagnostic tool.

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 tool takes zero parameters, so the baseline is 4. The description appropriately avoids inventing parameter detail and instead spends its space on return semantics, which the empty schema cannot convey.

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: 'Checks if the Fusion 360 add-in TCP bridge is running and responsive.' This is clearly distinguishable from every sibling, all of which create geometry, manage parameters, or export files.

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?

Explicitly says 'Use this tool first to diagnose bridge readiness before issuing modeling commands,' which gives a clear precondition for the whole sibling set. It does not state when not to use it (e.g. skipping after a successful check), so it falls short of full when/when-not coverage.

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