get_reef_feed_by_wallet

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

Annotations are absent, so description should compensate. It only states the function, but does not disclose behavior like whether it returns posts authored by or involving the wallet, or any pagination or ordering details.

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 single sentence, which is concise but lacks necessary detail to be fully informative. It earns its place but could be expanded.

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 or annotations, and the existence of sibling tools, the description is insufficient. Does not explain relationship to get_reef_feed or get_reef_post, nor any constraints.

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% and description adds no meaning. Does not explain what 'wallet' represents (author?) or what 'limit' does (max count? pagination?).

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 clearly states it retrieves reef posts filtered by a specific wallet. The verb 'Get' and resource 'reef posts' are specific, but lacks explicit differentiation from siblings like get_reef_feed.

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?

No guidance on when to use this tool versus alternatives (e.g., get_reef_feed for general feed). No context on prerequisites or typical use cases.

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