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 tool 'expands upon basic user inputs' and generates 'detailed, well-structured' content, but lacks critical behavioral details: permissions required, whether creation is idempotent, rate limits, or what happens on failure. For a write operation with zero annotation coverage, this is insufficient.

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 that efficiently convey the core functionality without wasted words. It's front-loaded with the main purpose and follows with elaboration. Minor room for improvement in tightening phrasing.

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 this is a write operation with no annotations and no output schema, the description is incomplete. It doesn't cover error handling, response format, or important behavioral constraints like authentication needs. For a tool that creates content in an external system, more context is needed.

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 documents both parameters thoroughly. The description adds marginal value by explaining that userInstructions are 'expanded into a comprehensive structure,' but doesn't provide additional syntax or format details beyond what the schema states. 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 clearly states the tool creates a Notion page with specific characteristics: 'Creates a rich, comprehensive Notion page that expands upon basic user inputs.' It distinguishes from siblings like get_notion_page (read) and update_notion_page (modify) by emphasizing creation and content expansion.

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 when needing to create detailed pages from simple inputs, but doesn't explicitly state when to use this vs. alternatives like update_notion_page or when not to use it. No prerequisites or 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?

With no annotations provided, the description carries full burden of behavioral disclosure. It effectively communicates the permanent nature of deletion ('cannot be undone'), which is crucial for a destructive operation. However, it doesn't mention permission requirements, rate limits, or what happens to linked content beyond the page itself.

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 perfectly concise with two sentences that each earn their place: the first states the action and scope, the second provides the crucial warning about irreversibility. No wasted words, front-loaded with the core functionality.

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 destructive operation with no annotations and no output schema, the description does well by emphasizing permanence and caution. However, it could be more complete by mentioning permission requirements or what the tool returns (e.g., success/failure confirmation). The high schema coverage helps compensate somewhat.

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 documents the single parameter (pageId) with its type, description, and warning. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score when schema coverage is high.

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 specific action ('permanently deletes') and resource ('a specified Notion page and all its contents'), distinguishing it from sibling tools like create, get, list, search, and update operations. It precisely communicates the destructive nature of the operation.

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 clear context for when to use this tool ('use with caution') due to its irreversible nature, but doesn't explicitly mention when not to use it or name specific alternatives. It implies usage for deletion scenarios but lacks explicit guidance on alternatives like archiving or moving content.

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?

No annotations are provided, so the description carries full burden. It mentions the return content but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or whether it's read-only (implied by 'Retrieves' but not explicit). This is a significant gap for a tool with no 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 appropriately sized and front-loaded, with two efficient sentences that convey purpose and return value without waste. Every sentence earns its place by adding 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?

Given no annotations, no output schema, and a simple input schema, the description is adequate but incomplete. It explains what the tool does and returns, but lacks details on behavioral aspects like permissions or errors, which are important for a retrieval tool in a Notion context.

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 documents the single parameter 'pageId' with its description. The description doesn't add meaning beyond what the schema provides, such as format examples or constraints. 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 clearly states the verb ('Retrieves') and resource ('specific Notion page'), specifying what it returns ('comprehensive details... including content, properties, metadata, complete page structure, nested content blocks'). It distinguishes from siblings like list/search tools by focusing on a single page retrieval.

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 for getting details of a specific page, but doesn't explicitly state when to use this vs. alternatives like list_notion_pages or search_notion_pages. It mentions retrieving 'comprehensive details,' which suggests depth, but lacks explicit guidance on prerequisites or exclusions.

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the operation as a list function with sorting and return metadata, which implies a read-only, non-destructive action. However, it does not address potential limitations such as pagination, rate limits, authentication requirements, or error conditions, leaving gaps in behavioral context.

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, well-structured sentence that efficiently conveys the tool's purpose, sorting, and return details without any redundant or extraneous information. It is front-loaded with the core action and appropriately sized for its complexity.

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 tool's low complexity (1 parameter, no output schema, no annotations), the description is mostly complete, covering purpose, sorting, and return metadata. However, it lacks details on behavioral aspects like pagination or error handling, which could be relevant for a list operation, preventing a perfect score.

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 input schema has 100% description coverage for its single parameter ('maxResults'), so the baseline is 3. The description adds value by specifying the sorting ('by last edited time') and return content ('key metadata including database title, schema, and last edited timestamp'), which are not covered in the schema, elevating the score to 4.

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 specific action ('Lists all accessible Notion databases'), resource ('Notion databases'), and scope ('in your workspace'), with additional details about sorting ('by last edited time') and return content ('key metadata including database title, schema, and last edited timestamp'). It distinguishes itself from sibling tools like 'systemprompt_list_notion_pages' by focusing on databases rather than pages.

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 for retrieving database metadata, but it does not explicitly state when to use this tool versus alternatives like 'systemprompt_search_notion_pages' or provide any exclusions. It lacks guidance on prerequisites or specific contexts where this tool is preferred, leaving usage inferred rather than clearly defined.

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?

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits such as sorting order and metadata returned, but lacks details on permissions required, pagination behavior, rate limits, or error handling. The description does not contradict any annotations, but for a tool with no annotations, it provides only moderate transparency.

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 front-loaded with the core purpose in the first sentence and adds essential details in the second, with no wasted words. It efficiently conveys the tool's functionality, sorting, and output in two concise sentences, making it easy to parse and understand quickly.

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 provides basic completeness by stating the action, sorting, and metadata returned. However, it lacks details on authentication needs, response format beyond metadata names, or limitations, which are important for a list operation with potential access controls. It is adequate but has clear gaps in context.

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 the single parameter 'maxResults' fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as default behavior or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description does not compensate but also does not detract.

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 specific action ('Lists all accessible Notion pages'), resource ('Notion pages'), and scope ('in your workspace'), with explicit sorting ('sorted by last edited time') and output details ('Returns key metadata including title, URL, and last edited timestamp'). It distinguishes from siblings like 'systemprompt_search_notion_pages' by emphasizing comprehensive listing without search filters.

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 for retrieving all pages in a workspace, sorted by recency, which provides clear context. However, it does not explicitly state when to use this tool versus alternatives like 'systemprompt_search_notion_pages' or 'systemprompt_list_notion_databases', nor does it mention exclusions or prerequisites, leaving some ambiguity in sibling differentiation.

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?

No annotations are provided, so the description carries the full burden. It mentions the search scope ('all accessible Notion pages') and what gets searched, but lacks critical behavioral details: it doesn't specify authentication requirements, rate limits, pagination behavior, error conditions, or what 'accessible' means in practice. For a search tool with no annotation coverage, this leaves significant gaps.

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 concise sentences that efficiently convey the core functionality. The first sentence states the action and scope, the second adds detail about what's searched. There's no fluff, but it could be slightly more structured (e.g., explicitly separating scope from 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?

Given the tool's moderate complexity (search operation), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and scope but lacks details on authentication, pagination, error handling, and output format. It doesn't fully compensate for the missing structured data, leaving the agent with incomplete operational context.

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 both parameters. The description adds no additional parameter semantics beyond what's in the schema descriptions. It mentions 'provided query' and 'relevant matches' but doesn't elaborate on query syntax, ranking, or result format. Baseline 3 is appropriate when the schema does all the work.

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's purpose: 'Performs a full-text search across all accessible Notion pages using the provided query.' It specifies the verb (search), resource (Notion pages), and scope (all accessible). However, it doesn't explicitly differentiate from its sibling 'systemprompt_search_notion_pages_by_title', which appears to be a more specific variant.

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 mentioning what gets searched (titles, content, metadata) and that it's for 'relevant matches.' However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'systemprompt_search_notion_pages_by_title' or 'systemprompt_list_notion_pages', nor does it mention any prerequisites or exclusions.

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?

No annotations are provided, so the description carries the full burden. It mentions the search behavior ('exact or similar title matches') which is useful. However, it doesn't disclose important behavioral traits like whether this is a read-only operation, authentication requirements, rate limits, pagination behavior, or what the return format looks like. The description adds some value but leaves significant gaps for a search 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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, and the second provides usage guidance. There's zero waste or redundancy, and the information is front-loaded appropriately.

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 that this is a search tool with no annotations and no output schema, the description should do more to explain what the tool returns and its behavioral characteristics. While it adequately covers the basic purpose and usage context, it doesn't address the output format, error conditions, or other operational details that would help an agent use it effectively.

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 both parameters. The description adds marginal value by reinforcing that the search can be 'exact or partial match' for the title parameter, but this is essentially restating what the schema already says. With complete schema coverage, the baseline is 3 even without additional parameter information in the description.

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's purpose: 'Searches specifically for Notion pages with titles matching the provided query.' It specifies the verb (searches), resource (Notion pages), and scope (by title). However, it doesn't explicitly distinguish this from the sibling tool 'systemprompt_search_notion_pages' which appears to be a more general search tool.

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 clear context for when to use this tool: 'Useful for finding exact or similar title matches when you know the page name.' This gives practical guidance about the appropriate scenario. However, it doesn't explicitly state when NOT to use it or mention alternatives like the general 'systemprompt_search_notion_pages' sibling tool.

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?

With no annotations provided, the description carries full burden but only partially discloses behavioral traits. It mentions 'preserving existing information' and 'maintaining page integrity,' which suggests non-destructive updates, but doesn't cover critical aspects like authentication requirements, rate limits, error conditions, or what happens if the pageId is invalid. The description is insufficient for a mutation tool with zero 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 appropriately sized with three sentences that are front-loaded with the core purpose. Each sentence adds value: the first states the action, the second explains the transformation process, and the third clarifies the scope of changes. There's minimal waste, though it could be slightly more concise.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success confirmation, updated page data), error handling, or important behavioral constraints. For a tool that modifies data, this leaves significant gaps in understanding its operation.

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 description coverage is 100%, so the schema already fully documents both parameters (pageId and userInstructions). The description adds some context about transforming 'simple inputs' into 'well-structured, detailed content,' but doesn't provide additional semantic meaning beyond what's in the schema descriptions. 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 clearly states the tool 'updates an existing Notion page with rich, comprehensive content based on user instructions' and distinguishes it from siblings like create_notion_page and delete_notion_page by focusing on modifying existing content. However, it doesn't explicitly differentiate from get_notion_page or search tools, which prevents a perfect score.

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 for enhancing, reorganizing, or expanding existing Notion page content, but doesn't explicitly state when to use this tool versus alternatives like create_notion_page for new pages or get_notion_page for reading. No clear exclusions or prerequisites are mentioned.

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