account_connection_instructions

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

The readOnlyHint and openWorldHint annotations already cover the safety profile. The description adds an important behavioral/security constraint: do not paste session files, SMS codes, or tokens into chat. It does not describe return content or enrollment steps, but it adds meaningful context beyond the annotations.

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 one tightly written sentence with the core purpose front-loaded before the security warning. It is appropriately sized for a zero-parameter informational tool, though 'local enrollment' is terse enough to be slightly under-specified.

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 zero-parameter, read-only tool, the description is minimally adequate. However, it does not say what the enrollment instructions cover, what the response will look like, or when to choose this over sibling account tools, leaving gaps for the invoking agent.

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 burden. The description neither contradicts nor needs to compensate for the empty schema; baseline 4 is appropriate.

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 and resource: 'Explain local enrollment.' It is clear enough to identify an informational enrollment-instructions tool, but it does not distinguish itself from sibling account tools such as account_check or account_refresh.

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 by the phrase 'Explain local enrollment' and the warning about not pasting secrets. The description gives no explicit when-to-use guidance, no exclusions, and no routing guidance versus the account-related siblings.

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