Mila

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 only says 'append' without disclosing side effects, permission requirements, or whether data is appended to the end of the tab. For a mutation tool with no annotation coverage, this is a significant gap in behavioral 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 a single, front-loaded sentence that states the purpose and key usage guidance without any redundant or filler content. Every part earns its place, making it exemplary in conciseness.

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 description explains the core operation and parameter usage, but with no output schema and no annotations, it lacks behavioral context such as return values, error conditions, or side effects. It is adequate for a simple append tool but leaves some gaps for an agent to fully understand the tool's behavior.

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 covers all parameters, but the description adds meaningful value by clarifying the distinction between 'rows' (multiple rows) and 'values' (single row). This goes beyond the schema descriptions and helps the agent choose the correct parameter format.

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: 'Append one or more rows of data to a spreadsheet tab.' It specifies the resource type (spreadsheet tab) and distinguishes it from sibling append tools like append_slides and append_to_document by explicitly mentioning spreadsheet/Excel/workbook tabs.

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 (appending data to a spreadsheet tab) and offers parameter guidance ('Use 'rows' for multiple rows or 'values' for a single row'). It does not explicitly state exclusions or when-not conditions, but the resource clarity effectively differentiates it from alternatives.

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 states the action ('append') but does not mention side effects, error behavior, permissions, or whether the operation is destructive. The description lacks details on what happens if the presentation ID is invalid or how the 'position' parameter affects the result beyond 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?

The description is a single, front-loaded sentence that immediately states the core functionality. The parenthetical '(slides, powerpoint, deck, keynote)' adds some redundancy but may help users recognize the resource type. No wasted words beyond that.

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 has nested objects (slide/slides) and no output schema, the description is thin. It does not explain what the tool returns, how to choose between 'slide' and 'slides', or the semantics of 'position' (though the schema covers the latter). For a mutation tool with this complexity, more context is needed for an agent to use it 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 input schema fully documents all parameters (100% coverage), so the description does not need to repeat their meaning. The description does add the notion of 'one or more slides', which aligns with the 'slide' and 'slides' parameters, but it does not clarify the relationship between them (e.g., mutual exclusivity). Since schema coverage is high, 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 uses a specific verb ('Append') and resource ('slides to an existing presentation'), clearly indicating the action and target. It distinguishes itself from siblings like 'create_slide_presentation' (which creates a new presentation) and 'append_rows' (which targets sheets). The parenthetical synonyms further clarify the resource type.

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 phrase 'existing presentation' clearly implies this tool is for modifying an already-created presentation, not for creating one. This provides clear context for when to use it, though it does not explicitly mention alternatives or when not to use it. The sibling tool names provide additional context for selection.

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, the description carries the burden of behavioral disclosure. It clearly states the core behavior (append, not replace) but omits other behavioral traits such as required permissions, response format, or error behavior. This is a minimum viable disclosure: clear on the primary action but missing important context for a mutation 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?

A single, front-loaded sentence that states its purpose and key constraint without any wasted words. Every element earns its place, covering action, resource, and nuance in one line.

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 simplicity of the tool (2 params, no output schema, no annotations), the description plus schema is nearly complete for invocation. It lacks notes on return values or failure modes, but these are minor for an append operation. The description covers the essential context: what to append, where, and to what.

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 covers 100% of parameters with descriptions, so the baseline is 3. The tool description does not add parameter-specific meaning beyond what the schema already provides (e.g., 'Document ID' and 'HTML content to append'), although the phrase 'to the end' reinforces content placement.

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 ('Append'), names the resource ('existing document'), and clarifies scope with 'to the end' and 'without replacing existing content.' This distinguishes it from update_document and other sibling tools like create_document, making the purpose unambiguous.

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 this tool (to add content without replacing) and even adds an explicit exclusion ('without replacing existing content'), which signals not to substitute it for update operations. However, it does not name alternative tools outright, so it stops 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?

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The only behavioral detail added is that content should be HTML, which is already stated in the input schema ('HTML content of the document'). The description does not mention side effects, permissions, return values, or success behavior, which is insufficient for a mutation 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 three short sentences: a clear action statement, explicit usage triggers, and a format constraint with an example. Every sentence earns its place, and the most important information is front-loaded.

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 description is adequate for a simple 3-parameter tool with fully specified schema, but it lacks any mention of output/return behavior, prerequisites, or side effects. Given that this is a create operation with no output schema and no annotations, more context would be expected for full completeness.

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 baseline is 3. The description adds only an example of HTML content ('<p>Hello</p>'), which is a minor reinforcement of the schema's 'HTML content' description. It does not materially enhance understanding of the other parameters (title, server_id).

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 action ('Create a new document') and lists synonyms for when to use it ('create, write, draft, or compose a document, doc, note, page, article, or word document'). This distinguishes it from sibling tools like `create_sheet` or `create_slide_presentation` by specifying the resource type.

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?

Explicit usage guidance is provided: 'Use this when asked to create, write, draft, or compose a document...' This gives clear context for when to invoke the tool. However, it does not name explicit alternatives or exclusions, so it falls short of a perfect score.

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 only states the core create action and 'initial tab', but does not mention return values, required permissions, side effects, or behavior when defaults are used. This is insufficient for a mutation tool without annotation support.

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, and the second sentence adds practical usage context. No wasted words or repetition of schema content.

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 six parameters, a nested object, and no output schema, yet the description omits any indication of what the tool returns (e.g., sheet ID or created object) or any prerequisites like server context. The schema covers parameters, but the description is too sparse for the complexity.

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 provides 100% description coverage for all six parameters, including detailed explanations of defaults and the cells object structure. The description adds no parameter-level information beyond the schema, so the baseline score 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 'Create a new spreadsheet' with synonyms (sheet, excel, workbook) and specifies 'with an initial tab', which distinguishes it from sibling tools like create_document and create_sheet_tab. The verb and resource are unambiguous.

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 when-to-use guidance: 'Use this when asked to create a spreadsheet, table, workbook, tracker, or organize data in rows and columns.' This clearly frames the intended usage, though it lacks explicit exclusions or named alternatives.

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. It only says 'Add a new tab' and does not disclose whether this modifies an existing spreadsheet, requires existing sheet_id, what happens on duplicate tab names, or what the response is. The mutation side effects are not explained.

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?

A single sentence, front-loaded with the action and target, no filler words. It is concise and readable while still conveying the core purpose.

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?

Despite full schema coverage, the tool involves a nested cells object and five parameters, and the description is only one sentence. It lacks context about how rows/columns/cells interact, optionality, constraints, or any behavioral guarantees for a mutation with no annotations or output schema. The agent would need to rely entirely on the schema.

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 explains each parameter (e.g., 'name' as 'Tab name', 'rows' as 'Number of rows'). The description adds no parameter-level meaning beyond the schema; the nested 'cells' object is only introduced by the schema, not by 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 action ('Add a new tab') and the resource ('to a spreadsheet'), with a helpful parenthetical clarifying terminology (sheet, excel, workbook). It distinguishes from 'create_sheet' by focusing on 'tab' rather than the workbook itself, but does not explicitly contrast with 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?

No guidance is provided about when to use this tool versus alternatives like create_sheet or update_sheet_tab. The description only states what the tool does; it does not mention prerequisites, exclusions, or scenarios where a sibling tool would be more appropriate.

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 must disclose behavior. It mentions slide structure (html, background, notes), but this repeats schema information and does not address side effects, prerequisites, or return values. For a create operation, more context about what happens after creation would be valuable.

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 concise at three sentences, front-loading the purpose and usage. There is minor redundancy between the synonym lists in the first two sentences, but overall it is efficiently 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?

With five parameters and no output schema, the description covers core purpose and usage but does not explain how parameters like server_id, theme, or aspectRatio affect execution, nor what response to expect. It is adequate but leaves notable 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 descriptions for all five parameters, so the baseline is 3. The description adds no new parameter-level meaning beyond repeating the slide object fields already documented 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?

The description explicitly states 'Create a new slide presentation' and includes synonyms (slides, powerpoint, deck, keynote), clearly identifying the verb and resource. It distinguishes from sibling tools like append_slides and update_slide_presentation by focusing on creation.

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 guidance with 'Use this when asked to create a presentation, slide deck, or slideshow,' indicating appropriate use cases. It does not explicitly mention alternatives or exclusions, but the 'create' framing contrasts with sibling operations.

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. The word 'permanently' explicitly communicates that the deletion is irreversible, which is crucial for an agent deciding whether to invoke this destructive tool. This goes beyond the tool name and provides important safety information.

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, front-loaded sentence with no redundant words. It efficiently conveys the action, permanence, target document types, and the required parameter.

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 delete tool with one parameter and no output schema, the description covers the essential context: what is deleted, what types, and that it is permanent. It could benefit from mentioning potential limitations (e.g., cannot delete non-document resources), but the clarity of the description makes the tool's function sufficiently complete for an agent.

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 already provides 100% coverage for the single parameter 'id' with the description 'Document ID'. The tool description's phrase 'by ID' merely restates the schema without adding additional meaning, such as ID format, source, or validation rules. Baseline of 3 is appropriate since the schema carries the semantic weight.

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 (permanently delete), the resource (a document), and specifies the document types (doc, word, note). It also distinguishes this from sibling delete_sheet and delete_slide_presentation tools by explicitly targeting documents.

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. It does not mention that this should be used only for documents, nor does it reference the sibling tools for deleting sheets or presentations. The only usage context is the requirement to provide an ID, which is a parameter prerequisite, not usage 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?

With no annotations provided, the description carries the full burden. It discloses that the deletion is permanent and cascades to all tabs, which are critical behavioral traits. It does not mention permissions or side effects, but the key implications are covered.

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 verb 'delete', and contains no redundant words. It efficiently conveys the full scope of the action.

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 one-parameter delete tool, the description fully covers the purpose, scope, and irreversibility. No output schema is needed, and the sibling context provides adequate alternatives for comparison.

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 covers the parameter with a description 'Sheet (workbook) ID'. The tool description adds some context about deleting the entire workbook, but this is more about behavior than parameter semantics, providing minimal additional value beyond 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 uses the specific verb 'permanently delete' and clearly identifies the resource as 'spreadsheet (sheet, excel, workbook)' with the scope 'and all its tabs'. This distinguishes it from siblings like delete_sheet_tab and delete_document.

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 this tool by stating it deletes the entire workbook including all tabs, making it apparent that delete_sheet_tab would be used for a single tab. However, it does not explicitly name alternatives or provide exclusion 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?

With no annotations, the description carries the full burden of behavioral disclosure. It discloses only the last-tab restriction, but lacks information about irreversibility, permission requirements, or effects on related data. For a destructive operation, this is a significant 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 one concise sentence that front-loads the core action and resource, followed by a critical constraint. No wasted words; every element earns its place.

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 2-parameter delete tool, the description is adequate but incomplete. It includes the key last-tab restriction but omits other important context such as permanence, permissions, and behavior when deletion fails. The absence of an output schema means return values are not explained, though that is not strictly required.

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% for both parameters ('Tab ID' and 'Sheet (workbook) ID'). The description adds minimal semantic context by clarifying that 'sheet' means spreadsheet, but does not elaborate on parameter formats or relationships. Baseline 3 applies as the 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 specifies the action ('Delete') and resource ('a tab from a spreadsheet'), with helpful synonyms in parentheses. This distinguishes it from sibling tools like delete_sheet (which would delete the entire spreadsheet) and other delete tools. The phrase 'Cannot delete the last remaining tab' further defines scope.

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 the tool is for deleting individual tabs, but it does not explicitly contrast with alternatives like delete_sheet. It provides a negative constraint ('Cannot delete the last remaining tab') but no positive guidance on when to use this tool versus others. Thus, usage is implied but not fully explicit.

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. 'Permanently delete' discloses the irreversible nature, which is important. It doesn't mention permissions or side effects, but for a simple delete-by-ID tool, this is adequate but not rich.

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 concise sentence, front-loaded with the essential verb and object. It wastes no words and includes useful synonyms in parentheses.

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 low-complexity tool with one parameter and no output schema, the description covers the core behavior and irreversibility. It could mention potential side effects or prerequisites, but the simplicity of the operation makes it nearly 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?

The input schema covers 100% of the parameter (id with description 'Presentation ID'). The description adds no extra semantic meaning beyond the schema, so the baseline score 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 states a specific verb ('delete') and a specific resource ('slide presentation'), with clarifying synonyms. It clearly distinguishes from sibling delete tools like delete_document and delete_sheet.

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 makes clear the tool is for slide presentations, providing context on when to use it. It doesn't explicitly mention exclusions or alternatives, but the resource type is unambiguous given the tool name and synonyms.

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. It discloses the return payload (title, HTML body, metadata) but does not explicitly state that the operation is read-only or safe, nor mention error behavior. The verb 'Get' implies no side effects, but is not fully explicit.

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, focused sentence that front-loads the core purpose and includes relevant output details. No waste 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 read operation with one parameter and no output schema, the description provides sufficient context by stating what is returned. It is complete enough for an agent to invoke correctly and understand the response.

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 already fully describes the sole parameter (id as 'Document ID') with 100% coverage. The description only repeats 'by ID' and does not add format details, examples, or additional context, so no value beyond 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 uses a specific verb ('Get') and resource ('document') with precise scoping ('by ID'), and enumerates what is included ('title, HTML body, metadata'). It clearly distinguishes from sibling tools like list_documents or get_sheet.

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 retrieving a specific document's full content by ID, which is distinct from listing or creating. It does not explicitly name alternatives or exclusions, but the context is strong enough for an agent to infer when to use it.

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 the return scope: all tabs and cell data in A1 notation, which is useful for understanding the operation's output. However, it does not explicitly state it is a read-only operation or mention potential performance implications of retrieving all tabs, leaving some behavioral aspects implicit.

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 is front-loaded with the core action ('Get a spreadsheet... by ID') and concisely states the key return detail (all tabs and cell data in A1 notation). There is no redundancy or unnecessary elaboration.

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?

With only one parameter and no output schema, the description adequately covers the tool's core function and expected return. It clearly states the result includes all tabs and cell data in A1 notation. It could specify whether formulas, formatting, or empty cells are included, but for a simple get-by-ID tool, this is sufficient. It omits error handling or size caveats, but those are not critical for a basic retrieval.

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 already provides a full description of the id parameter ('Sheet (workbook) ID'). The description repeats this with synonyms but adds no additional meaning about the parameter's format, constraints, or usage details. Schema coverage is 100%, so the description offers only marginal value beyond 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 clearly states the tool retrieves a spreadsheet by ID, including all tabs and cell data in A1 notation. This distinguishes it from sibling tools like get_sheet_tab, which likely retrieves a single tab, and from get_document. The parenthetical synonyms (sheet, excel, workbook) remove ambiguity about what type of resource is meant.

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?

There is no explicit when-to-use guidance or mention of alternatives. The phrase 'including all tabs and their cell data' implies this is for full-sheet retrieval, but it does not directly state when to use this over get_sheet_tab or other list tools. The usage context is implied rather than clearly stated.

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, the description carries the burden of disclosing behavior. It mentions that the tool returns all cell data in A1 notation, which is a useful detail, but it does not state read-only status, error behavior, or permissions.

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 concise sentence that front-loads the core action and resource, while including the key return-format detail without any wasteful wording.

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 tool with two well-documented parameters and no output schema, the description adequately covers the primary behavior and return format. It lacks edge-case handling details, but these are not critical for such a straightforward 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?

Both parameters have full descriptions in the input schema (100% coverage), so the description does not need to add parameter-level detail. It adds no extra semantic value beyond what the schema already provides.

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 ('get'), the resource ('single tab'), and the scope ('from a spreadsheet'). It distinguishes from siblings like get_sheet by specifying 'single tab' and adding the detail about A1 notation.

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 wording implies use when retrieving a specific tab's data, but there is no explicit guidance on when to use this tool versus alternatives like get_sheet or list_sheets. No exclusions or alternative recommendations are provided.

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 must carry the full burden of disclosing behavioral traits. 'Get' implies a read operation, but the description does not explicitly state it is non-mutating or safe, nor does it mention authentication, rate limits, error cases, or pagination. The only added behavioral detail is that all slide data is included, which is minimal.

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, front-loaded sentence that immediately communicates the main purpose. Every word contributes: 'Get', the resource type, synonyms, 'by ID', and the inclusion of all slide data. No verbosity 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 tool with one parameter and no output schema, the description gives the core purpose and a hint of the return content ('all slide data'). However, it omits important context such as the shape of the returned data, any prerequisites, and how it relates to sibling tools. Since there is no output schema, the description should provide a bit more detail to be fully self-sufficient.

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 the parameter 'id' described as 'Presentation ID'. The description's 'by ID' adds no new meaning beyond the schema. According to the rubric, with high schema coverage the baseline is 3, and there is no additional value to raise the score.

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 'Get' and the resource 'slide presentation', with synonyms (slides, powerpoint, deck, keynote) to disambiguate. The phrase 'by ID' specifies the lookup mechanism and 'including all slide data' defines the scope, distinguishing it from sibling tools like get_document or get_sheet.

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?

There is no guidance on when to use this tool versus alternatives such as list_slides or get_document. The description does not mention prerequisites (e.g., need to obtain the ID via a list operation) or any exclusions, so the agent receives no decision support for tool selection.

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. It discloses key behaviors: 'Supports pagination, sorting, and filtering by workspace.' This maps to the parameters and sets expectations for how the tool operates. It does not describe the return format or any side effects, but for a read-only list tool, this is adequate. The phrase 'List all documents' alongside 'Supports pagination' is slightly nuanced but clarified.

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-loads the core purpose, and every sentence earns its place. The first sentence states the action and scope, the second provides usage guidance and feature highlights. There is 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 there is no output schema, the description could be expected to explain return values, but 'List' implies a list of documents. It covers the purpose, when to use the tool, and the main features (pagination, sorting, filtering). It does not mention default behaviors (e.g., default sort order or limit) but is reasonably complete for a tool with five optional parameters and no annotations.

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 baseline is 3. The description adds a high-level summary ('pagination, sorting, and filtering by workspace') that groups the parameters and clarifies that server_id represents a workspace. This adds a small amount of semantics beyond the schema but does not go into new depth.

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 with a specific verb ('List') and resource ('documents'), and even enumerates the types ('docs, word, notes, pages'). It distinguishes itself from sibling tools by focusing on documents, not sheets or slides, and provides a clear usage trigger.

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 says to 'Use this when asked to list, find, or search documents, notes, drafts, or written content.' This is clear when-to-use guidance. However, it does not explicitly mention alternatives like list_sheets or list_slides, nor does it state when not to use the tool. Given the sibling names, the resource distinction is obvious, but the absence of explicit exclusions keeps this at a 4.

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 discloses that only accessible workspaces are returned ('you have access to'), but does not mention return format, pagination, or explicit read-only behavior. This is minimal but not misleading.

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 with no filler. It includes the necessary scope clarification ('you have access to') without redundancy. Perfectly 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?

With no output schema and zero parameters, the description gives the essential information: what is listed and the access constraint. It does not specify the exact return structure, but for a simple list operation, this is minimally sufficient and not incomplete.

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 tool has zero parameters, and the schema confirms this (coverage 100%). The description adds meaning by clarifying that 'all' accessible workspaces are listed, reinforcing the parameterless nature. Baseline for 0 parameters is 4, and no further parameter explanation is needed.

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 specific verb 'List' and the resource 'workspaces (servers)' with an explicit scope 'you have access to'. It clearly distinguishes from sibling list tools (e.g., list_documents, list_sheets) by referring to a distinct resource type (servers/workspaces).

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: this tool lists all accessible workspaces. It doesn't explicitly mention alternatives or when-not-to-use, but the resource distinction from other list tools implies usage. No exclusion criteria are needed for a parameterless list operation.

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, the description carries full disclosure burden. It states the return scope ('tab metadata') and explicitly excludes 'cell data,' which is an important behavioral trait. However, it does not mention pagination or any other side effects, though for a list operation these omissions are minor.

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 action and purpose, and every phrase adds value ('no cell data' prevents misinterpretation). 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?

For a list operation with 5 optional parameters and no output schema, the description adequately conveys the core behavior and use case. It could be more complete by mentioning the return structure (e.g., array of spreadsheet objects with tabs), but the mention of tab metadata gives sufficient 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 baseline is 3. The description does not add any meaningful parameter information beyond what the schema already provides, despite referencing search/find use cases that rely on the filter-like parameters.

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 'List all spreadsheets' with a specific resource and scope ('sheets, excel, workbooks'). It also distinguishes from siblings by emphasizing tab metadata and explicitly excluding cell data, setting it apart from list_documents and list_slides.

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 guidance with 'Use this when asked to list, find, or search spreadsheets, workbooks, tables, or tabular data.' This clearly indicates when to use the tool, though it does not mention alternatives or when not to use it, which keeps it at 4 rather than 5.

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 for behavioral disclosure. The verb 'list' implies a read-only operation, which is a basic behavioral trait. However, it does not disclose any details about pagination behavior, default limits, or how server_id filtering affects results. The description is minimally transparent but sufficient for a simple list operation.

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 main action, and uses parenthetical synonyms to clarify scope. Every word adds value; there is 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?

The description is complete for a simple list tool: it states what it lists and when to use it. There is no output schema, but the tool name and description imply a list of slide presentations. It does not explain return format or default pagination, but the schema covers parameters, and the behavior is straightforward. Slightly more detail about response structure would elevate 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 description coverage is 100%, so all five parameters have descriptions in the schema. The tool description itself adds no additional parameter semantics beyond the word 'all,' which loosely relates to the absence of required filters. The baseline of 3 applies because the schema already documents parameters thoroughly.

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 function with a specific verb and resource: 'List all slide presentations' and provides synonyms (slides, powerpoint, deck, keynote). It distinguishes from sibling tools like list_documents and list_sheets by focusing specifically on slide presentations.

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 the tool: 'Use this when asked to list, find, or search presentations, decks, or slideshows.' However, it does not mention alternatives or when not to use it (e.g., when a specific presentation is needed, use get_slide_presentation), so it lacks explicit 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 full burden. It discloses that content replaces the entire body, which is a key behavioral trait. However, it does not mention auth requirements, reversibility, error cases, or return format, so it is only minimally transparent.

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, front-loaded with the purpose, and no waste. Efficiently states what the tool does and what parameters are needed.

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 mutation tool with no output schema and no annotations, the description covers the main purpose and behavior (replaces body). It lacks details on return values and error handling, but given the simplicity and high schema coverage, it is adequate.

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 each parameter described in the schema. The description adds the 'and/or' relationship between title and content, clarifying the combination, but does not add significant meaning beyond 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 clearly states the verb 'update', the resource 'document', and specifies the document types (doc, word, note) and what can be changed (title/content). This distinguishes it from sibling tools like create_document or append_to_document.

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 existing documents and mentions 'and/or' for title/content, but it does not explicitly contrast with alternatives like create_document or append_to_document. It lacks explicit when-not-to-use 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?

No annotations are provided, so the description carries full burden. It mentions 'workbook-level' and 'currently only title,' but omits side effects, permissions, response format, or reversibility—significant gaps for a mutation 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?

One sentence, front-loaded with the verb 'Update,' and no wasted words. The parenthetical synonyms are mildly redundant but not harmful, making it appropriately 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?

For a simple 2-parameter tool with no output schema, the description covers purpose and scope adequately. However, it omits return value or error behavior, leaving a moderate gap in completeness.

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 covers both parameters fully, so the description adds no extra parameter semantics beyond noting that title is the only updatable property. The baseline score 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 it updates workbook-level properties of a spreadsheet, specifically title, using a specific verb and resource. This distinguishes it from sibling tools like update_sheet_tab, which likely target tab-level properties.

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 updating workbook-level properties and notes the current limitation to only title. It doesn't explicitly mention alternatives like update_sheet_tab, but the context is clear enough for basic decision-making.

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 must disclose mutation behavior. It does clarify that null clears a cell, but it fails to explain whether updates are partial or full, whether permissions are needed, or what return value to expect. The misleading 'merge cells' claim is particularly problematic for an agent relying on this text.

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 short and front-loaded with the action and resource. The second sentence adds a meaningful behavioral note. The phrase '(sheet, excel, workbook)' is slightly cluttered but not harmful.

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?

With 7 parameters, a nested cells object, and no output schema, the description is too terse. It omits update semantics (e.g., whether unspecified fields remain unchanged), required ID dependencies, and any response details. The unsupported 'merge cells' capability further undermines completeness.

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%, so the baseline is 3, but the description adds little beyond category-level restatements (rename, color, resize). It incorrectly introduces merge operations not present in the schema, and it does not clarify the nested 'cells' object structure beyond what the schema already provides.

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 identifies the tool as updating a spreadsheet tab and lists operations such as rename, color change, resize, and clearing cells. However, it includes 'merge cells' which is not supported by the schema, and the parenthetical '(sheet, excel, workbook)' adds ambiguity. It does distinguish from sibling tab operations by explicitly mentioning 'tab'.

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 modifying an existing tab's properties or content, but it does not explicitly state when to use this tool versus alternatives like create_sheet_tab or update_sheet. There are no exclusions, prerequisites, or references to sibling tools.

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, the description carries the full burden of behavioral disclosure. It only says 'update' without mentioning that the data field performs a full replacement of slide objects, nor does it disclose any destructive aspects, permissions, or reversibility. This is a significant gap for a mutation 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, front-loaded sentence that efficiently conveys the tool's purpose and scope. 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?

Given the tool's complexity (5 parameters, no output schema, no annotations), the description is too brief to be fully complete. It doesn't explain the full-replacement semantics or any side effects, though the schema compensates for parameter details. 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%, so the parameters are well-documented in the schema. The description lists the same fields without adding extra meaning beyond what's in the schema. Baseline 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 clearly states the tool updates a slide presentation and lists the specific attributes: title, slide data, theme, or aspect ratio. It uses a specific verb+resource and distinguishes itself from siblings like create_slide_presentation and update_document.

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 updating an existing presentation but doesn't explicitly mention when to use it vs alternatives like create_slide_presentation or append_slides. There is no exclusion or alternative guidance, so it meets the 'implied usage' criterion.

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