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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are scoped to "this deployment's tier," it explains how to obtain a full-tier token, and it states "Needs no arguments," all of which affect how an agent interprets partial results.

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 trigger condition followed by a dense but purposeful enumeration of outputs. The parenthetical list of enum categories is long but each item maps to a distinct decision an agent must make, so it earns its space; the closing "Needs no arguments" is a compact and useful call-shape note.

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?

An output schema exists, so return structure need not be restated, and the description still summarizes the semantic contents of the response. Combined with the tier caveat and the no-arguments note, an agent has everything required to decide to call this tool first and to interpret what it gets back.

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 the baseline is 4, and the description reinforces this by explicitly stating "Needs no arguments," removing any doubt that an empty object is correct. No additional per-parameter meaning is needed or possible here.

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 uses a concrete verb ("Returns") and then enumerates exactly what is returned: available tools, an intent-to-tool map, every valid enum value (profile hints, strategy slugs, descriptor names, assets, thesis slugs), the Generate/Challenge/Revise/Present workflow, sign and unit conventions, and full-tier token instructions. This is unmistakably an onboarding/discovery tool and cannot be confused with any domain sibling such as build_portfolio or describe_regime.

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?

"USE WHEN you are new here, or need the valid values and the right tool for a task" gives a clear, front-loaded trigger condition covering both onboarding and enum-lookup use cases. It stops short of an explicit when-not or naming a competing tool, but for a zero-argument entry-point tool there is no realistic alternative to route away from.

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