searchRecent

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

No annotations are provided, so the description carries full burden. It mentions the 7-day time constraint, which is useful behavioral context. However, it doesn't disclose other important traits: whether this is a read-only operation, rate limits, authentication requirements, pagination behavior (implied by 'next_token' but not explained), or what format results return. For a search tool with 10 parameters, this is inadequate behavioral disclosure.

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 a single, efficient sentence that states the core functionality. There's zero waste or redundancy. It's appropriately sized for a tool with good schema documentation.

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 search tool with 10 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'posts' refers to (tweets?), what the search scope includes, how results are returned, or any limitations. The 7-day constraint is mentioned, but other critical context about behavior and results is missing.

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 all parameters are documented in the schema. The description adds minimal value beyond the schema - it only implies that 'recent' means 'last 7 days' which relates to time parameters but doesn't provide additional semantic context about individual parameters. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Search recent posts (last 7 days)' clearly states the action (search) and resource (posts) with a time constraint. However, it doesn't distinguish this tool from its sibling 'searchAll' which presumably searches all posts without the 7-day limitation. The purpose is understandable but lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives like 'searchAll' or other search-related siblings. It mentions the 7-day constraint but doesn't explicitly state this is for recent-only searches versus comprehensive searches. No prerequisites, exclusions, or comparison to other tools are provided.

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