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

The annotations already declare the tool as read-only, idempotent, non-destructive and not open-world. The description adds useful behavioral context beyond them: it works as a plain GET with no sign-in and returns duplicate true with matches and web addresses, plus already_sent true for an unreviewed contribution.

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 front-loaded with the purpose and then gives concrete usage examples and return semantics. The URL examples are long but useful, and the prose is otherwise efficient.

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?

The tool is simple, all four parameters are documented, and annotations cover safety. Because there is no output schema, the description appropriately explains the key return values, though it could be slightly more explicit about the false case.

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%, so the schema already documents kind, title, name and date. The description's examples reinforce which parameters pair with event versus place, but they add little meaning beyond the schema's own field descriptions.

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 states a specific verb and resource: it checks whether Little Milwaukee already holds an event, place or business. The phrase 'before you research or send it' distinguishes this pre-submission duplicate check from research-oriented siblings such as search_places and from submission tools such as submit_event.

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 gives clear usage context: call it before researching or sending an event, place or business. It does not explicitly name alternatives or state when not to use it, but the intended workflow is clear.

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