grove_flagged

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

The description mentions the permission requirement (grove_read) but adds no information about side effects, return format, pagination, or rate limits. The read-only nature is already implied by the annotation, so the description adds little beyond what's already known.

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 extremely concise, using only two sentences to convey the essential purpose and parameters. There is no redundancy or unnecessary detail, making it efficient and easy to parse.

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 simple list tool, the description provides enough context for the primary use case, but it omits the 'app_id' parameter and does not elaborate on the behavior of flags (e.g., whether they are boolean or have states). Given the tool's simplicity, it is reasonably complete but not fully comprehensive.

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?

The description explains the 'flag' parameter by listing valid values and clarifies 'channel_name' as an optional restriction. However, it omits the 'app_id' parameter present in the schema, leaving its purpose unexplained. Schema coverage is 2 of 3 (66%), and the description adds some meaning but is incomplete.

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 the action (List) and the resource (messages) with a specific filter (by flag). It distinguishes from other grove tools by focusing on flags, though it doesn't explicitly differentiate from grove_search or grove_get_history.

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?

It provides some usage context: 'across all channels (or one channel)' and mentions the permission 'Requires grove_read.' However, it does not explain when to prefer this tool over alternatives like grove_search or grove_get_history for listing messages.

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