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

The description goes well beyond the annotations (which only flag it as a non-destructive write) by disclosing the approval workflow: public sources go live immediately unless an admin disabled auto-approval (then they wait for review), and private ones are only readable by linked nodes. It also names the return fields and the rejected-with-reasons behavior. This is rich, non-obvious behavioral context.

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?

Three tight sentences: purpose first, then approval/visibility behavior, then return shape. Every sentence carries information and nothing is padded.

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?

With an output schema present, full input schema coverage, and annotations declaring the mutation profile, the description supplies exactly the missing behavioral context (approval flow, node visibility) an agent needs to call it correctly.

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 100%, and the schema already documents the sources array structure and agent_name semantics in detail. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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?

States a specific verb (suggest) and resource (groups/subreddits/searches where people sell tickets) that clarifies the tool's output well beyond the name. However, it does not distinguish this from nearby siblings like add_my_sources or submit_seller_leads, so an agent must infer the boundary.

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?

Usage is implied by 'suggest new groups,' but there is no explicit guidance on when to use this versus add_my_sources or submit_seller_leads, nor any stated prerequisites. The agent can guess, but the choice among similar-sounding tools is not made clear.

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