get_new_since

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

Without annotations, the description provides important behavioral details: it queries (read operation), returns deduplicated and sorted output, and requires a Supabase connection. This covers the main behavioral traits, though it doesn't disclose error handling or empty-result 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 concise sentences, front-loaded with the primary action, followed by key output details and a prerequisite. Every sentence adds value.

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 simple 1-parameter tool with no output schema, the description is fairly complete: it covers what the query does, what it returns, and a requirement. Minor absences like pagination or empty results don't undermine adequacy.

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?

The schema covers the sole parameter 'since' with 100% description coverage, so the baseline is 3. The description only restates that rows are created after the timestamp, adding no new meaning beyond the schema.

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?

Description uses a specific verb 'Queries' targeting Supabase cache rows with a temporal filter, and specifies the return behavior (deduplicated news items sorted newest first). This clearly distinguishes it from sibling tools like search_today or get_trending_news.

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 context for using this tool (fetching cache rows after a timestamp) is implied, but there is no explicit comparison to alternatives or exclusions. It doesn't reference sibling tools or state when not to use it.

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