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

The description confirms 'Read-only; no signature', which is useful context beyond the annotations that already declare readOnlyHint=true and destructiveHint=false. Pagination defaults and maximums are also stated. However, it does not describe authentication requirements or what happens with the caller parameter beyond the schema.

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 a compact paragraph with front-loaded purpose and key behavioral traits. Every sentence adds some value, though a bit more separation between purpose, caller semantics, and pagination could improve scannability.

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 a simple read operation, the description covers the essentials: scope, read-only nature, caller semantics, and pagination. Still, it omits the return shape and any filtering/ordering behavior, leaving an agent with minor uncertainty about what exactly is returned.

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 100%, so the schema itself documents all three parameters thoroughly. The description repeats the pagination details (default 50, max 200) and clarifies 'caller' as the account whose view to read, but adds little beyond the schema descriptions.

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 ('Get caller's paid inbox') and defines the exact content: 'messages from non-contacts who paid the inbox fee'. This clearly distinguishes it from siblings like geode_messaging_get_my_inbox or geode_social_get_account_paid_messages.

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 description explains what the tool returns but gives no guidance on when to use it versus alternatives such as get_my_inbox or social paid message tools, and no prerequisites or exclusions are mentioned.

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