note1.ai

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds key context: the calendar event is untouched, and the series can be canceled. This clarifies the destructive scope, which is valuable beyond annotations.

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 and a clarifying caveat. No filler or redundancy.

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 cancellation tool with full schema coverage and adequate annotations, the description covers the essential behavioral nuance (series option, calendar event untouched). Slight gap: no mention of what happens to existing recordings, but this is not critical for selecting the 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 100%, so parameters are well-documented. The description adds meaning to cancelSeries by linking it to 'optionally the whole recurring series', which helps the agent understand the boolean's effect. teamId and meetingId remain as in 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?

The description uses a specific verb ('Calls off') and resource ('note1's recording bot') with clear scope ('for a meeting (optionally the whole recurring series)'). This clearly distinguishes it from sibling tools like note1_schedule_recording, which would set up the bot.

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 implies when to use it: when you want to cancel a recording bot for a meeting, optionally including the series. It does not explicitly mention alternatives, but the context makes it evident from siblings. Missing explicit exclusion like 'do not use to delete calendar events' but the last sentence covers that.

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

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

Annotations already declare readOnlyHint: true and destructiveHint: false, covering the safety profile. The description adds useful context about 'paste-ready' output and 'speaker-attributed' transcripts, but it does not disclose deeper behaviors like error handling or handling of missing meetings. This meets the baseline given annotation coverage.

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 long, front-loads the core purpose, and includes a clear usage condition. Every word earns its place, with no redundancy or filler.

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 the read-only annotation, complete parameter schema, and the tool's export-focused role, the description provides enough to understand what to expect and when to invoke it. It does not describe the exact return structure, but the lack of an output schema and the straightforward export function make this a minor gap.

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%, with each parameter (meetingId, format, teamId, content) already described in the schema. The description reinforces the meaning of 'summary/transcript' and 'markdown/json' but does not add any semantics beyond the structured schema, so the baseline of 3 applies.

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 action: 'Export a meeting's summary and/or full speaker-attributed transcript as paste-ready markdown (or structured JSON).' It specifies the verb (export), the resource (meeting summary/transcript), and the output variants, effectively distinguishing it from sibling tools like note1_get_meeting.

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 explicit use-case guidance: 'Use when the user wants the complete content, verbatim quotes, or a document to save.' However, it does not name specific alternatives or state when not to use it, leaving the differentiation from similar retrieval tools implicit.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'List' is consistent. The description adds value by mentioning recording status, but does not disclose behavior about limit/upcoming defaults or teamId being ignored, though teamId is covered in the schema.

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?

Single concise sentence that front-loads the action and resource, with no wasted words.

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?

The tool is simple with no required parameters and no output schema. The description explains the return value concept (calendar events with recording status), but could mention pagination or default upcoming behavior; however, it is adequate for the simplicity.

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 67%: teamId and upcoming have descriptions, but limit is undocumented. The description itself adds no parameter details, so it fails to compensate for the missing limit explanation.

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 uses a specific verb 'List' and resource 'calendar events', and adds the key detail of recording status, which distinguishes it from sibling tools like note1_list_meetings or note1_get_meeting.

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 implies usage by stating it lists calendar events with recording status, but it does not explicitly state when to prefer this tool over alternatives such as note1_list_meetings or note1_search_meetings.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds value by detailing what the returned meeting includes, which is helpful since there is no output schema. However, it does not disclose additional behavioral aspects such as error handling, permissions, or rate limits, so a middle score is appropriate.

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 sentence, front-loaded with the primary action ('Fetch one meeting') and efficiently itemizing the returned content. There is zero redundancy; every word contributes to understanding the tool's behavior.

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 read-only fetch with two parameters and no output schema, the description covers the essential purpose and expected result composition. It does not mention error cases or how to obtain a meetingId, but the schema description already indicates that meetingId comes from search/list/calendar results. Overall, it is sufficiently complete for straightforward use.

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%, with both meetingId and teamId having meaningful descriptions. The description adds no parameter-specific details beyond what the schema already provides, so the baseline of 3 is warranted.

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 tool fetches a single meeting and enumerates the returned components (summary overview, summary sections, participants, status, dashboard link). It is specific with a verb and resource, and the word 'one' provides some distinction from list/search siblings, though it does not explicitly name alternatives.

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 explicit guidance on when to use this tool versus alternatives like list_meetings or search_meetings. There are no prerequisites, exclusions, or contextual cues beyond the implication that you need a specific meetingId. This falls under 'no guidance' rather than 'implied usage' because the description does not even hint at selection criteria.

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

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

Beyond the readOnlyHint annotation, the description discloses that the tool does not create calendar events but returns a link, and that note1 is pre-invited to record. This gives useful behavioral context about the tool's side effects and workflow.

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 key purpose ('THE tool'), and every clause adds value. It avoids repetition and is well-structured.

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 tool with no output schema, the description clearly states what is returned (prefilled link), the user action needed, and note1's involvement. It doesn't mention timezone default or platform limitations, but those are covered by the schema, making it sufficiently complete.

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 coverage is 100% and both parameters (platform and timezone) have descriptions. The description adds no per-parameter detail, but the schema already handles semantics, so a baseline score of 3 is appropriate.

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 explicitly states it is 'THE tool for schedule/set up/book a meeting requests,' making the purpose unmistakable. It also clarifies it returns a prefilled calendar link rather than creating events, distinguishing it from sibling tools like note1_schedule_recording.

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 clearly dictates this is the tool for scheduling requests, and explains that it cannot create events directly, which guides the agent to use this link-based approach. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of full exclusion guidance.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the browsing context and filter options but does not disclose pagination behavior or response format, which is a gap for a list tool.

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 sentence that front-loads the core behavior (browse without search query) and lists filters concisely. There is no redundancy or fluff.

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?

The tool has five optional parameters and no output schema. The description covers the core purpose and filters but omits pagination cursor usage and expected return shape, which are relevant for a list operation. Adequate but with clear gaps.

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 coverage is 100% with all parameters documented. The description mentions status and date range, which maps to the schema, but does not add new semantic detail beyond what the schema already provides. Baseline 3 is appropriate.

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 uses the verb 'Browse' with the resource 'note1 meetings', and explicitly states 'without a search query', which distinguishes it from the sibling search tool. This gives a specific, actionable purpose.

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 clearly implies this tool is for browsing meetings when no search query is needed, and mentions filtering by status and date range. However, it does not explicitly name alternative tools or exclusion scenarios, so it falls short of full explicit guidance.

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

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

Annotations already indicate the tool is not read-only, not open-world, and not destructive. The description adds meaningful behavioral context by stating it schedules a recording bot and does not create calendar events or send invitations, clarifying side-effect boundaries. It could go further by explaining behavior when both calendarEventId and callUrl are provided, but this is a minor gap.

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 primary action, then provides mode details and an explicit exclusion with an alternative. Every sentence earns its place with no redundancy or fluff.

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 6 optional parameters, no output schema, and sibling tools, the description is complete: it explains the two operational modes, sources for inputs, and clearly demarcates non-actions. The combination instructions and explicit 'does NOT' phrase cover the main edge cases, making it sufficient for an agent to invoke correctly.

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 already provides 100% coverage for all parameter descriptions, so the baseline is 3. The description adds value by grouping parameters into two use modes (calendarEventId vs. callUrl + callAt) and by indicating where calendarEventId can be obtained (note1_get_calendar), which helps the agent select the correct parameter combination.

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 tool schedules note1's recording bot, and distinguishes it from siblings by specifying it handles either existing calendar events or ad-hoc meeting links. It also explicitly notes what it does NOT do (create calendar events or invite), which further sharpens the purpose.

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 explicit usage scenarios: use calendarEventId for existing events (sourced from note1_get_calendar) or use callUrl + callAt for ad-hoc recordings. It also gives an alternative tool (note1_get_scheduling_link) when the user needs to create a calendar event or invite, making when-to-use vs. not-to-use clear.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context: searches respect the user's own permissions, and the two modes return different outputs (ranked snippets vs AI answer). This goes beyond the annotations and clarifies expected behavior, though it omits pagination or rate-limit details.

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 then elaborates on modes and permissions. Every sentence earns its place, with no fluff or repetition of annotation data.

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 two modes and four parameters, the description covers the key differentiator (mode behavior) and the security/permission model. It does not explain the 'kind' filter or result ordering, but the input schema provides the available enum values. Without an output schema, it could mention return format, but the mode descriptions give a fair clue. Overall, it is sufficiently complete for an agent to select and invoke the 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 coverage is 75% with descriptions for query, mode, and teamId. The description adds meaning to 'mode' by explaining the output difference between 'search' and 'analysis'. The 'kind' parameter is not discussed beyond its enum values, but the enum is self-descriptive. This is adequate but not outstanding; the description adds some value over 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?

The description states a specific action ('Search your note1 meetings') with resource and scope. The two modes ('search' and 'analysis') add functional clarity. It does not explicitly differentiate from sibling tools like note1_list_meetings, but the verb 'search' and mention of ranked snippets and AI answers imply a distinct purpose.

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 implies usage: use this to search meetings with a query, using either 'search' or 'analysis' mode. However, it does not provide explicit when-to-use guidance or alternatives, such as 'use note1_list_meetings to browse without a query' or 'use note1_get_meeting to retrieve a specific meeting transcript'. No exclusions are mentioned.

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

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

Annotations already mark destructiveHint=true, and the description adds valuable behavioral nuance: time/link changes retarget only note1's bot and do not affect calendars. It also clearly states it does not create events or invite users, going beyond the annotation to describe side effects and boundaries.

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 main purpose, and every sentence contributes useful information. No redundant phrases or filler.

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 mutation tool with 9 parameters and no output schema, the description covers the core purpose, key side effects, and provides an alternative tool. It lacks commentary on series behavior or output, but the schema handles parameter-level details. Overall context is sufficient for an agent to decide to use it.

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 coverage is at 78%, with descriptions for most parameters (e.g., callAt as 'New ISO start time', style examples). The description lists the editable fields but does not add deeper meaning beyond what the schema already provides. Some parameters like teamId and applyToSeries are not mentioned in the description, but they are covered in 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?

Clearly states it 'Edits a note1 meeting/recording' and lists specific editable fields (title, bot time or link, summary style, language, video). It also explicitly distinguishes itself from note1_get_scheduling_link by clarifying it does NOT create calendar events or invite attendees, differentiating it from sibling tools.

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?

Provides explicit when-not context: 'Does NOT create a calendar event or invite anyone' and names the alternative tool to use for that purpose. Also explains the scope of time/link changes (bot only, attendees' calendars untouched), giving clear guidance for when this tool is appropriate.

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