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

The description states it 'Returns' data, consistent with the readOnlyHint and idempotentHint annotations. It does not contradict the annotations, and while it adds no extra behavioral context beyond what annotations provide, the annotations already cover the safety profile, so a high score is appropriate.

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?

The description is concise, beginning with a clear question and then listing the exact outputs in a structured manner. It contains no superfluous words or repetition, and every sentence adds value.

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 parameterless read-only tool, the description is complete. It specifies exactly what information is returned (agents, manifests, checklist, config, and next steps), which is sufficient for an agent to understand the tool's functionality and when to invoke it. No additional context is needed.

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?

With zero parameters, there is nothing to describe beyond the schema. The description does not add parameter-specific detail because none exist. Per the rubric, 0 params yields a baseline of 4, and the description meets that baseline without need for compensation.

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 clearly states the tool's purpose as checking onboarding status and enumerates specific outputs (registered agents, capability manifests, progress checklist, testnet config, and actionable next steps). It is specific and distinguishes this tool from siblings like register or get_recommended_action.

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?

The description implies usage through the question 'Where am I in onboarding?' but does not explicitly state when to use this tool versus alternatives. It lacks direct guidance such as 'Use this when you need to review your onboarding status' or any comparison with sibling tools.

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