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

Annotations already declare read-only, idempotent, open-world and non-destructive semantics, so the safety bar is largely met structurally. The description adds a genuinely useful behavioral fact beyond them: reads require no authentication. It does not describe pagination, caching or freshness of the catalog counts.

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 tight sentences with no filler. The capability scope is front-loaded ahead of the supporting auth detail.

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 usefully sketches what comes back (capability groups, onboarding links, catalog counts) and confirms no auth is needed. Given zero parameters and rich annotations, this is close to sufficient; a note on whether counts are live or cached would complete it.

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 there is no parameter semantics to document; baseline is 4. The description does not need to compensate for any schema gap.

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 ('Read') and a well-enumerated resource (public discovery, preparation, contribution and task-memory capabilities, CLI onboarding links, catalog counts). It distinguishes itself from the skill-oriented siblings implicitly by returning hub-level metadata rather than skill data, but never names those siblings explicitly.

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?

There is no when-to-use statement, no condition that selects this tool over find_robot_skills or inspect_robot_skill, and no exclusions. The only guidance is the auth note, which is a constraint rather than usage routing.

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