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

With no annotations, the description carries the full burden and mostly delivers: it declares read-only behavior, that no input is taken, and that no state is changed. It also warns that answers are deployment-specific ('which key types this deployment can prove', 'whether enrollment is switched on'), which prevents an agent from assuming universal behavior. It does not say whether the caller must already be authenticated, which is the main remaining behavioral gap.

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?

A single sentence, front-loaded with the core purpose and then the content list, followed by a short behavioral clause. The enumerated list is dense but every item corresponds to something an enrolling agent needs; nothing is redundant or padded.

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?

There is no output schema and no annotations, so the description must preview the return content, which it does thoroughly by naming each section of the guide. Given a parameterless read-only documentation tool, that is close to complete; only the authentication requirement and any ordering/dependency caveats are unstated.

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 applies. The description reinforces this by stating 'no input', telling the agent it can invoke without assembling arguments.

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 gives a specific verb ('Read') plus a precise resource ('how an AI agent enrolls with this Obelisk Gate') and then enumerates the exact contents: endpoints in order, per-endpoint fields, provable key types, enrollment enabled/disabled, and account sign-up posture. That is enough to separate it from siblings like gate_status or verify_token without opening any schema.

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?

Usage is only implied: an agent that needs to know how to enroll should read this first. The description never states when to call this versus gate_status, transparency_head, or verify_token, and gives no explicit prerequisites or exclusions. The read-only/no-input note hints at safe consultation but is not routing guidance.

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