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

With no annotations, the description carries the burden and discloses key behavior: the tip is NOT immediately published, enters a manual review queue, and is anonymous/unassociated with any user or organization. It does not mention response behavior or auth requirements, but the most decision-relevant traits are covered.

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 dense and front-loaded with purpose, then behavioral caveats, usage guidance, and formatting rules. The date-format sentence is somewhat redundant with the schema but earns its place as a quick-reference. No filler sentences are present.

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 one-parameter tool with no annotations or output schema, the description covers purpose, usage timing, moderation behavior, anonymity, and input completeness guidance. Minor gaps remain: it does not state what a successful submission returns, nor explicitly instruct the agent to verify the event is absent before calling create_event_tip.

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% with detailed per-field explanations and formats, so a baseline of 3 is appropriate. The description adds a global 'include as much detail as possible' instruction and a concrete date/time example, slightly reinforcing but not significantly extending what the schema already provides.

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 opens with a specific verb and resource: 'Submit a tip about a flea market event discovered from an external source.' It clarifies the tool's role versus the read/search siblings by saying it is for event information that does not yet appear in the Svapp database. This makes the tool's purpose unambiguous.

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 explicitly states 'Use this when you find event information that does not yet appear in the Svapp database,' which gives clear context for selection. It does not explicitly name alternatives like search_events or get_event, but the read-vs-write contrast with sibling tools is strongly implied.

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