solver_sync_source_deployments

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

With no annotations, the description carries the burden and does well: it discloses persistence, the active-connection requirement, and the caveat that unevidenced identities are never persisted. It does not fully specify whether the sync removes previously persisted deployments or what happens on failure, so it is not a 5.

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 dense sentences deliver purpose, endpoint, prerequisite, and a key caveat without redundancy. Front-loaded with the core action, then scoping constraints.

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 single-parameter tool with no output schema or annotations, the description covers purpose, side effect, prerequisite, and non-certification boundary. It is missing only explicit return/error detail, which is minor given 'answers the synced deployment set'.

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 0%, but the description compensates by embedding connection_id in the endpoint and requiring it to be an ACTIVE tested connection. It adds meaningful semantic context beyond 'string'. It stops short of explaining how to obtain the ID or accepted formats.

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 precise action ('Discover and persist') and resource ('connection-authorized, certification-backed deployments'), plus the exact endpoint. It also disambiguates from certification by noting discovery is not certification, making the tool's role clear among siblings.

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?

Clearly states the prerequisite (ACTIVE/tested connection), which signals when this tool is appropriate relative to test/list flows. It also implies it should follow connection testing, but it doesn't explicitly name alternative tools or state when not to use it.

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