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

With no annotations, the description carries the full burden, and it does disclose two useful behaviors: ideas are backed by real underlying finds and are not repeated within a week. It omits, however, whether ideas are pre-generated versus computed on demand, what authorization or api_key scope is needed, and any pagination or rate-limit behavior.

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?

Two sentences with little padding, but the middle clause is garbled and self-referential ('turn them on per saved search or tracker with daily_ideas'), which costs the reader more than it delivers. The useful scoping constraint (no repeats within a week) is not front-loaded.

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?

An output schema exists, so return values need not be described. But with no annotations and zero schema description coverage across three parameters, the description leaves too much unexplained — particularly the 'days' window and source filtering, which are the primary knobs for this tool.

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% for three parameters, so the description must compensate and largely does not. 'Per saved search or tracker' loosely hints at source_id, but 'days' (default 7, max 60) and 'api_key' are never explained, leaving the agent to guess at the lookback window and authentication behavior.

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 conveys the resource — daily idea sets backed by real finds, deduplicated within a week — and even names the equivalent REST endpoint. However, there is no explicit verb ('get'/'list'/'fetch') in the main clause, so the agent must infer retrieval from the 'Same as GET /v1/ideas/daily' aside. It gives some differentiation from write_ideas but does not clearly separate it from list_finds or tracker_feed.

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 phrase 'turn them on per saved search or tracker with daily_ideas' is self-referential and reads like documentation boilerplate rather than guidance on when to call this tool. There is no statement of when to prefer this over write_ideas, list_finds, or tracker_feed, and no prerequisites or exclusions.

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