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

Annotations already declare readOnly, idempotent, openWorld=false, and destructive=false. The description adds useful 'no auth' information and clarifies that the tool searches the /tools directory. Repeating 'Read-only' is redundant but not harmful.

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 compact and front-loaded: it states the purpose, the trigger, the fallback action, and access requirements in three short sentences. No wasted words.

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 single-parameter read-only lookup with no output schema, the description conveys purpose, trigger, and scope. It doesn't spell out the return format, but 'check whether' plus the filing workflow makes the expected result reasonably clear. Minor gap only.

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 coverage is 100% and the single query parameter is already well described with examples ('app name, e.g. a screener or charting tool'). The description adds little beyond that, but the schema carries the meaning, so the baseline of 3 is appropriate.

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-resource pairing: 'check whether EventTrader already has a page for a financial app (the /tools directory)'. It clearly scopes the tool to the Build it Better workflow and distinguishes it from generic search tools among the siblings.

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 says 'Call this before filing' and explains that an app already present can still be filed by sending improvements, which gives a clear trigger and subsequent action. It does not name specific alternative tools or list when not to use it, but the workflow guidance is solid.

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