add_to_radar

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

No annotations are provided, so the description carries full burden. It discloses that the tool requires an API key and has a free tier limit, but does not explain idempotency, overwrite behavior, or return value. The behavioral context is minimal for a mutation tool.

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 two sentences with no fluff. It efficiently conveys purpose and a key prerequisite. However, it could be more structured by separating the purpose from the requirement.

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 five parameters (two required) and no output schema, the description lacks essential details about parameter usage, return values, and the 'Radar' concept. The tool's complexity requires more information for correct invocation.

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 the description does not describe or provide meaning for any of the five parameters. Without compensating information, an AI agent cannot understand how to fill required fields like 'title' and 'url'.

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 tool saves a discovered event/community to the user's Radar in Your Echo Agent for specific downstream actions like calendar add, contact extraction, and AI-drafted outreach. It distinguishes from discovery tools (discover_events, discover_communities) and outreach drafting tools.

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 mentions the prerequisite ECHO_API_KEY and free tier limit, but does not explicitly state when to use this tool versus alternatives like extract_contacts_from_url or draft_outreach_for_event. It implies usage after discovery but lacks clear when-to-use and when-not-to-use guidance.

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