Fellow MCP Server

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it's a write operation (sync to database), has incremental vs. full sync modes, and mentions performance implications ('This is slower' for transcripts). However, it doesn't cover error handling, authentication needs, or what 'sync' entails beyond fetching.

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 two sentences, front-loaded with the core purpose and followed by specific usage guidance. Every sentence earns its place with no redundant or vague language, making it highly efficient and easy to parse.

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?

Given no annotations and no output schema, the description adequately covers the tool's purpose and key usage scenarios. However, as a write operation with performance implications, it could benefit from more detail on error handling, what 'sync' entails (e.g., overwriting, merging), or expected output format.

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 the schema already fully documents all three parameters. The description adds minimal value beyond the schema, only mentioning 'force=true for full re-sync' which is already in the schema description for 'force'. No additional syntax or format details are provided.

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 clearly states the verb 'sync' and the resource 'meetings from Fellow API to local database', specifying both source and destination. It distinguishes from siblings by focusing on data synchronization rather than retrieval or querying of specific meeting components like transcripts, participants, or summaries.

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 explicitly provides when to use alternatives: 'By default does incremental sync (only new/updated since last sync). Use force=true for full re-sync.' This gives clear guidance on parameter-driven behavior selection, though it doesn't mention when to use this tool versus sibling tools like get_sync_status.

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