get_assembly_capabilities

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

With no annotations, no output schema, and no parameter documentation, the description carries the full behavioral burden and does not meet it. 'Check' weakly implies a read-only operation, but nothing is said about what is returned, whether it can fail, or whether the result should be cached or re-fetched per session.

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?

One short sentence with the action front-loaded and the timing hint trailing it; nothing is redundant. It is arguably too terse rather than too long, but structurally it is clean.

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 zero-param discovery tool with no output schema and no annotations, the description should at minimum characterize the returned capability information so an agent knows how to act on it. It establishes the pre-flight intent but leaves the payoff undefined.

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 schema baseline is 4 and there is nothing further for the description to disambiguate. No parameter-level gaps exist.

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 verb/resource pair ('Check' + 'assembly capabilities') indicates a discovery call that returns protocol and operation support, but 'native addon protocol' is jargon and the description never says what a capability report actually contains. It also does not distinguish this from nearby lookalikes such as check_assembly or get_rpc_status.

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?

'before working' implies a call-first sequencing hint, which is genuinely useful for a gating/discovery tool. However, there are no explicit conditions, no statement of when it can be skipped, and no named alternatives among the many assembly siblings.

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