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

The annotations indicate readOnlyHint=false (implying a write/mutation) and idempotentHint=false (not safe to retry). The description aligns with these by implying a state-changing enrollment action. However, it lacks additional behavioral context such as whether existing enrollments are overwritten, whether attestation is irreversible, or if there are prerequisites. Given the annotations already flag non-read-only and non-idempotent, the description adds minimal value beyond that.

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 a single sentence, concise and front-loaded with the core action. There is no redundancy. However, a brief additional sentence on the expected body structure or when to use it would significantly improve utility without much bloat, but as is, it is effectively concise.

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?

Given the tool's complexity (likely involves compliance, attestation, and multiple integration points), the description is minimal. There is no output schema, and the input schema is opaque. The description does not mention required fields, potential side effects, or how it fits into the broader workflow (e.g., must be called before delegate_authority). It is adequate for a high-level understanding but incomplete for confident invocation.

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 schema has a single required 'body' parameter with additionalProperties: true and no schema description coverage. The description does not clarify what the body should contain, such as organization details, terms acceptance, or attestation payload. It only mentions 'current terms and agent attestation' which gives a hint but not a concrete structure. Since the schema is nearly opaque, the description falls short of compensating fully, hence a 3.

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 states a specific verb ('Enroll') and a specific resource ('accountable live organization') with qualifying details ('current terms and agent attestation'). It clearly distinguishes from sibling tools like enroll_agent and create_rights_holder, both of which have different scopes. The mention of 'Launch gates' adds operational context.

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 when to use the tool: to enroll a live organization, presumably before operations like delegation or submission. However, it does not explicitly state when NOT to use it or name alternatives like enroll_agent. There is no guidance on how it differs from enrolling an agent, which is a critical distinction given the importance of attestation and terms.

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