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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts the annotations cannot express: it is free, requires no API key, and needs no account — real auth and cost constraints. It does not describe result shape beyond the field list, which keeps it at 4.

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?

Two sentences, front-loaded with the 'what you can call right now' framing and closing with the actionable 'call it FIRST' directive. The first sentence is a dense four-item enumeration that reads as a run-on, but every clause carries distinct information.

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?

With no output schema, the description carries the burden of explaining return content, and it does so by listing the four manifest categories. Combined with the no-auth, no-cost disclosure, an agent has enough to call it and interpret results; only the shape of the returned data (per-tool entries vs. lists) is left unspecified.

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 of 4 applies; there is no parameter surface for the description to clarify or omit.

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 description names a specific resource (this connection's access manifest) and enumerates exactly what it contains: free-to-call tools, right-gated tools, owned robots, unlockable robots. That is far more informative than the title. It stops short of naming or contrasting any sibling tool, so an agent must infer that no hardware_*/software_* tool overlaps.

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?

It gives an explicit sequencing directive ('Call it FIRST') with the rationale that it avoids trial calls that will be refused, which implicitly steers the agent away from probing gated tools. There is no stated case for when not to call it or an explicit alternative, so it falls short of full 5-level guidance.

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