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

Beyond the annotations, the description discloses non-obvious behavior: it auto-selects a sole active Schwab credential, performs a token-refresh readiness check, and by default triggers a no-trade broker snapshot run through the Vault-backed runtime-secret path. It also clearly states sanitization and that raw secrets, account numbers, and Vault ids are never accepted or returned. Rate limits and return shape are not covered.

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 front-loaded with the purpose and key behavior before listing security constraints. It is somewhat dense, especially the long list of never-accepted/returned data, but each sentence largely serves a purpose for a security-sensitive smoke test.

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 no output schema and only minimal annotations, the description covers the important purpose, default behavior, credential auto-selection, diagnostic opt-in, and security posture. It remains incomplete on return values and on the log-related parameters, but is otherwise sufficient for an agent to call it correctly in common cases.

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?

Schema description coverage is 0%, so the description must compensate. It meaningfully explains brokerCredentialId auto-selection, includeDiagnostics behavior, and the default snapshot run associated with runSnapshot, but it leaves logLimit and includeLogs completely undocumented.

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: an MCP smoke test for an authenticated user's saved Schwab broker connection. The phrase 'one-stop' distinguishes it from single-purpose siblings such as get_broker_token_refresh_status and get_broker_account_snapshot, since it combines readiness checks with an immediate snapshot run.

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 implicit usage is clear as a smoke test, and the description explains auto-selection behavior when brokerCredentialId is omitted. However, it never explicitly names sibling alternatives (e.g., get_broker_token_refresh_status or get_broker_account_snapshot) or says when not to use this composite test.

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