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

Discloses it's free, polls Authority, and lists possible statuses. No annotations exist, so description must carry full burden; lacks details on authentication, rate limits, or error behavior.

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?

Concise two sentences with front-loaded purpose. Could include structured parameter info, but no wasted words.

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?

Output schema exists, so return values are covered, but description lacks parameter semantics and prerequisites. For a 2-param tool with 0% schema coverage, more context is needed for reliable 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?

No parameter descriptions in schema (0% coverage) and description provides no explanation for 'dpop_token' or 'authority_npub'. Agent cannot infer parameter purpose from description alone.

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?

Description clearly states verb ('Check') and resource ('adoption-request status'), and distinguishes from siblings by focusing on status checking. No sibling tool has similar purpose.

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?

Implied usage for checking adoption status, but no explicit when-to-use or alternatives. Related tool 'schwab_request_adoption' exists but no guidance on selecting.

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