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

Annotations already establish read-only, idempotent, open-world behavior, and the description adds two non-obvious pieces of context: pagination is passed through to the upstream API, and token status is not proof of tradeability. Those are real operational caveats beyond the structured data, though return shape and rate-limit behavior are unmentioned.

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?

Two tight sentences with the core scope front-loaded and no filler. The tradeability caveat is slightly cryptic but still earns its place as a warning.

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 five-parameter, open-world list tool with no output schema and no documented parameters, the description covers purpose and one data caveat but omits what a result record contains and how sorting/search affect results. It is minimally adequate, not complete.

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 bears full responsibility, yet it only alludes to pagination ('upstream pagination') without explaining page/limit interplay. The sortBy enum options, sort direction, and search matching behavior are entirely undocumented, leaving four of five parameters unexplained.

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 and resource ('List/search tokens from the public Limitless API') and adds scope with 'including pending tokens,' which separates it from get_token_detail and get_trending. It does not name sibling tools explicitly, so the differentiation is inferable 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?

There is no explicit guidance on when to use this versus get_token_detail, get_trending, or get_listing_status. The caveat about tradeability hints at a use boundary but never states when-not or which alternative to pick.

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