search_activities

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

With no annotations, description carries burden. It discloses search scope (titles and content) and mentions FTS5. However, it does not describe side effects, rate limits, or whether it returns only current user's activities. Still, for a read-only search tool, transparency is adequate.

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, no filler. Front-loaded with purpose and usage guidance, followed by concrete examples. 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?

Lacks descriptions for 4 of 5 parameters and no output schema. Does not explain return format, pagination, or which fields are searchable beyond titles/content. Incomplete for a tool with 5 parameters.

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 has 5 parameters with only 'query' described (coverage 20%). Description adds no new meaning beyond the schema's description for 'query'. Other params (start, end, source, limit) have no descriptions in schema or description, leaving their semantics unclear.

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 clearly states it performs keyword search (FTS5) over activity titles and content, using specific verb 'search' and resource 'activities'. It also distinguishes from sibling semantic_search_activities by specifying the search type (keyword vs semantic).

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?

Explicitly tells when to use this tool: 'for concrete terms and phrases' and advises preferring it over semantic_search_activities for keyword-shaped queries. Provides concrete examples ('deploy decision', 'retry strategy') and an alternative tool.

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