token_bowl_chat_get_direct_messages

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

No annotations are provided, so the description carries the full burden. It discloses the return shape (message fields plus pagination metadata) and the limit ceiling, but says nothing about ordering, pagination mechanics, authentication, or whether messages are marked read as a side effect.

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-loaded purpose statement followed by clearly labeled Args and Returns sections; each line earns its place, though the Returns block is somewhat redundant given the output schema exists.

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 single-parameter read tool with an output schema, the definition covers purpose, the parameter's constraints, and the broad response shape; only ordering and pagination behavior remain unstated but these are minor for a list-fetch tool.

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 0% and the schema only declares a bare integer with a default, so the description adds real value by stating the parameter's meaning, its default of 20, and a max of 50 that appears nowhere in the schema. It fully compensates for the single undocumented parameter.

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 gives a specific verb+resource ('Fetch private direct messages') and scopes it to messages 'sent to or from your account,' which distinguishes DMs from the general get_messages sibling. It does not explicitly name siblings like get_unread_direct_messages, so differentiation is implicit rather than stated.

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?

'Use this to retrieve your one-on-one private message conversations' implies the usage context but offers no when-not guidance and does not mention alternatives such as get_unread_direct_messages for filtering to unread DMs.

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