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

With no annotations, the description carries the full burden and does well: it discloses that the Typebar team is notified with account identity and submitted numbers, that turnaround is typically within a day, and that the account email is contacted. It stops short of explaining the authorization parameter or whether repeated requests are rate-limited, so it is strong but not exhaustive.

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?

Front-loads the core promise ('in ONE call'), then uses labeled WHEN TO USE / WHAT HAPPENS / ALTERNATIVES sections. Every sentence carries actionable content with no filler.

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 request tool with no output schema and no annotations, the description supplies trigger conditions, effect and timeline, contact channel, and waiting-period alternatives. An agent has everything needed to decide and call it correctly.

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 coverage is 83%, so the schema does most of the work; the description only loosely alludes to 'the numbers you send' without adding format or meaning. It does not compensate for the undocumented 'authorization' parameter, so the baseline 3 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?

States a specific action (request a higher scale limit for your account) and emphasizes 'ONE call', immediately distinguishing it from any retry/upload sibling. The trigger (413 with DOCUMENT_TOO_COMPLEX or SESSION_TOO_FULL) makes the intent unambiguous.

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?

Explicit WHEN TO USE gated on two specific error codes, plus a named set of ALTERNATIVES with sibling tools (init_session, close_session_document, upload as attachment). Leaves nothing about timing or fallback to inference.

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