studiomcphub

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

The description adds cost information ($5.00 / 50 GCX) beyond the annotations, which already declare read-only and non-destructive behavior. There is no contradiction with annotations. However, additional behavioral details like expected output format or rate limits are missing.

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 very concise, using a single sentence to convey the core function, scope, and pricing. No unnecessary words, and key 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?

While the description covers purpose and cost, it lacks details about the return format (e.g., whether it returns a zip file or individual assets), pagination behavior, or what metadata fields are included. Given no output schema, these gaps reduce 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?

The input schema has 100% description coverage, so the description does not need to add parameter details. It reiterates the minimum quantity but does not provide new semantic context 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's function: bulk download metadata and images from a specific dataset (Alexandria Aeternum). It distinguishes itself from sibling tools by emphasizing the bulk nature and minimum quantity.

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 bulk downloads with minimum 100 artworks but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. No exclusion criteria or sibling tool comparisons 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds only 'FREE', which is not a behavioral trait. It does not disclose response details, rate limits, or prerequisites beyond what annotations provide.

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 short sentence that conveys the purpose effectively. However, the redundancy of 'FREE. (FREE)' wastes space without adding value. Still, it is mostly efficient and 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?

For a simple tool with one required parameter and no output schema, the description provides essential context (what is checked) and notes it is free. It lacks details about the return format or possible errors, but given the low complexity and rich annotations, it is minimally 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 a clear description for the wallet parameter. The tool's description does not add additional meaning (e.g., format examples or notes) beyond what the schema already states. Baseline of 3 is appropriate given full schema coverage.

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 the tool checks 'GCX credit balance, loyalty rewards, and volume tier', providing a clear verb and resource. The sibling tools are diverse and unrelated, so no ambiguity arises. The repeated 'FREE' emphasizes no cost but does not detract from clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by stating what it checks and that it's free, but it offers no guidance on when to choose this tool over siblings (e.g., when needing balance vs. asset info). No alternatives or exclusions are mentioned, leaving the agent to infer context.

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

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds no behavioral context beyond noting it is free. No disclosure of rate limits, data freshness, or error states.

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?

Very short at two sentences, but 'FREE. (FREE)' is redundant and wastes space. Could be more concise without the repetition, but overall not bloated.

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, the description should explain the content or structure of a compliance manifest. It does not mention default parameter values or what 'all' regulation means for output. Leaves significant gaps for a tool dealing with legal documents.

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 schema already describes both parameters. The description adds minimal value by vaguely hinting at dataset usage but does not explain defaults, formats, or provide concrete semantics 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 verb 'Get' clearly indicates retrieval, and the resource is specified as 'compliance manifests for dataset usage' with specific regulations (AB 2013 and EU AI Act Article 53). It distinguishes from siblings as no other tool deals with compliance manifests.

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 on when to use this tool vs alternatives, nor any prerequisites or when-not-to-use scenarios. The 'FREE' label is present but does not provide actionable usage direction.

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

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

Annotations indicate readOnly and idempotent; description adds that output is TIFF with embedded DPI, providing useful behavioral context. No contradictions.

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 but includes redundant 'FREE. (FREE)' text. Still, it is efficient and to the point.

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?

No output schema exists, and description does not detail return value structure beyond output format. Input encoding is in schema, but overall completeness is adequate but not thorough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and describes all parameters. Description adds that output is TIFF, which is not in schema, providing extra value beyond the baseline 3.

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 ('convert'), the resources ('sRGB and CMYK color profiles'), and the context ('essential for print production'). It distinguishes from sibling tools as the only color profile conversion 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 implies use for print production but does not explicitly state when not to use or list alternatives. However, among siblings, no other tool serves this purpose, so ambiguity is low.

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?

Description adds no behavioral context beyond annotations. Annotations already indicate destructive and idempotent; 'FREE' is ambiguous and uninformative.

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?

Very short, but includes redundant 'FREE. (FREE)' that serves no purpose. Could be streamlined without this 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?

Does not describe return value or side effects. With no output schema, description should hint at result (e.g., success/error) to be complete for simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions fully cover both parameters. Description does not add extra meaning beyond 'Asset key to delete' and wallet address 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?

Clearly states 'Delete an asset from your wallet storage,' specifying the action and resource. Distinguishes from siblings like save_asset and get_asset.

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 on when to use this tool versus alternatives like archive or remove. No prerequisites or conditions mentioned.

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

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

Annotations indicate the tool is not read-only (readOnlyHint=false) and not destructive. The description adds context about costs, tiers, and optional features like Soul Whisper, implying metadata embedding. However, it does not explicitly state whether the tool modifies the asset in place or simply returns generated metadata, leaving room for confusion about side effects.

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 and well-structured, starting with the core function, then detailing tiers, and finally optional features. It uses a bullet-like format with parentheses for cost. One minor improvement would be to separate cost info from the description, but overall it is efficiently written.

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 absence of an output schema, the description should explain what the tool returns. It describes the generated metadata for each tier but does not specify the return format or whether it modifies the asset. This is a significant gap for a tool with 9 parameters and no output schema, making it only partially complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with each parameter having a clear description. The tool description adds some high-level context about customization but does not significantly enhance understanding beyond what the schema already provides. The baseline score of 3 for high coverage 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 is an AI-powered artwork analysis tool with two distinct tiers, specifying the outputs for each. This differentiates it from sibling tools like infuse_metadata, which likely handle raw metadata injection rather than AI generation. The verb 'enrich' combined with the tier details leaves no ambiguity about the tool's purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as infuse_metadata or other metadata tools. There is no mention of prerequisites, when not to use, or how to choose between this and similar tools. The focus is entirely on the tiers, not on usage context.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context: it explicitly states the tool is free ('FREE'), and details the returned data (percentages, CSS names, complementary colors) that go beyond the input schema. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences plus a repeated 'FREE. (FREE)' which is redundant. The first sentence effectively states functionality, but the second sentence lists use cases which, while helpful, could be more concise. The repetition of FREE is unnecessary and wastes space.

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?

No output schema exists, but the description compensates by specifying return types (hex/RGB/HSL, percentages, CSS names, complementary colors). All 3 parameters are fully documented in the schema. Annotations provide safety hints. The only missing piece is not explicitly stating that the image must be Base64-encoded (though the schema parameter description covers it). Overall, the description is sufficiently complete for a read-only color extraction tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for all 3 parameters (image, format, num_colors), each with clear descriptions. The description mentions 'returns hex/RGB/HSL colors' which maps to the format parameter but adds no new meaning beyond the schema. It also mentions 'percentages' which is not a parameter. Thus description provides marginal added value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action (extract dominant color palette) and the resource (from an image). Lists specific return values (hex/RGB/HSL colors, percentages, CSS names, complementary colors) and use cases (design systems, mood boards, color matching). Sibling tools include other image operations but no other palette extraction, so it is well distinguished.

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?

Mentions use cases ('Great for design systems, mood boards, and color matching') but does not provide explicit when-to-use or when-not-to-use guidance relative to sibling tools. No alternative tools are named or exclusion criteria given. The 'FREE' tag hints at cost but not usage context.

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

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds value by specifying cost ($0.10/GCX), token range (500-1200), and 'signed' image URL, providing context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with cost note, no wasted words, front-loaded with key information.

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 tool with one parameter and no output schema, the description sufficiently explains output (metadata + signed URL) and cost. Minor gap: no explicit mention of output format (likely JSON), but inferable.

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?

Single parameter 'artifact_id' is fully described in the schema (including example). The description does not add additional parameter meaning beyond what the schema 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?

Clearly states the tool retrieves Human_Standard metadata and a signed image URL for a museum artwork, distinguishing it from siblings like 'get_asset' and 'search_artworks' by specifying the resource type and output details.

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 use for museum artwork retrieval with metadata and signed URL, but lacks explicit guidance on when to prefer this tool over similar siblings like 'get_asset' or 'get_artwork_oracle'.

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

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds context about output tokens (2K-6K), cost ($0.20/2 GCX), and the AI nature of the analysis, enhancing transparency beyond the schema and annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, comprising two to three sentences with no redundant information. It front-loads the key output and includes essential details about the analysis type and cost.

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 simple parameter set and no output schema, the description adequately describes the output. However, it lacks explicit usage context compared to siblings, slightly reducing 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% with a single parameter artifact_id. The description does not add new information about the parameter beyond what the schema provides, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves a 'Hybrid_Premium 111-field NEST analysis' plus an image, specifying the type of deep AI visual analysis including color palette, composition, symbolism, and emotional mapping. This distinguishes it from siblings like get_artwork or extract_palette.

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 use when detailed analysis is needed but does not explicitly state when not to use or compare to alternatives. Cost is mentioned, suggesting careful use, but no direct guidance on selecting between siblings.

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

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's addition of 'FREE' adds minimal behavioral context. It does not describe return format or error conditions, but given the annotations cover safety, the description adequately reinforces the read-only nature.

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 very short but contains redundancy ('FREE' repeated twice). It could be more concise without the repetition, but it is not overly verbose.

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?

No output schema is provided, and the description does not mention what the tool returns (e.g., asset data). For a retrieval tool, this omission is significant; the description should indicate the output structure or at least confirm that the full asset is returned.

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 both parameters 'wallet' and 'key' fully described. The description does not add additional meaning beyond what the schema provides, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the verb 'Retrieve' and specifies the resource 'stored asset from your wallet storage by key', clearly distinguishing it from sibling tools like list_assets (which retrieves all) or delete_asset.

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 explicit guidance on when to use this tool versus alternatives; the description only states what it does. It fails to mention that this is for retrieving a single asset by key, while list_assets or search_artworks might be more appropriate for other use cases.

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

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe, non-destructive behavior. The description adds one detail (usage examples) but does not contradict annotations. With annotations providing baseline transparency, a score of 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, clear and front-loaded. The '(FREE)' tag adds minor contextual value but is not necessary. Overall efficient without excess.

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, full schema coverage, and rich annotations, the description provides enough context: purpose, usage guidance, and mention of examples. The absence of an output schema is acceptable given the tool's nature.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the schema includes a clear description and example for the single parameter 'tool_name'. The tool description itself does not repeat parameter details, but the schema already handles semantics adequately.

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 'Get the full JSON Schema and usage examples for a specific tool,' using a specific verb and resource. It also distinguishes from sibling tool 'search_tools' by advising use after it.

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 says 'Use after search_tools to load only what you need,' which provides clear when-to-use context. It does not explicitly mention when not to use, but the guidance is sufficient for a simple retrieval 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?

Annotations indicate idempotentHint=true (safe to retry) and destructiveHint=false (not destructive). The description adds value by naming the underlying library (ExifTool), detailing the two modes, mentioning the dependency on 'enrich_metadata' for the full_gcx mode, and disclosing the cost. There is no contradiction with annotations. The description provides behavioral context beyond what annotations alone convey.

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 (two sentences) and front-loaded with the main action. It efficiently conveys purpose, modes, and cost without extraneous information. While it could benefit from a slightly more structured presentation (e.g., bullet points for modes), it remains clear and to the point.

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 (3 parameters, nested object, two modes, cost, external tool dependency), the description covers the essential aspects: what the tool does, its modes, the required input format, and cost. It also references the associated tool 'enrich_metadata' for the full_gcx mode. There is no output schema, but the description does not need to explain return values. It is adequately complete for an agent to use the tool 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 has 100% description coverage, so the baseline is 3. The description adds meaningful semantics: it explains that 'metadata' for full_gcx should be the output of 'enrich_metadata', and it lists the fields included in each mode. This helps the agent understand the expected structure beyond the schema's enums and types.

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: 'Embed metadata into image via ExifTool.' It specifies two distinct modes ('standard' and 'full_gcx') with clear field lists, differentiating it from siblings like 'enrich_metadata' which prepares metadata, or 'watermark_embed' which embeds watermarks. The verb 'infuse' combined with resource 'metadata' and the explanation of modes makes the purpose highly specific.

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 explains the two modes and when each is appropriate: standard for limited XMP/IPTC fields, full_gcx for the complete Golden Codex namespace. It also notes the default mode and references the cost per use. However, it does not explicitly state when NOT to use this tool, such as for non-image files or when no external tool is available. Overall, the guidance is clear but could be more comprehensive.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds that the tool returns sizes and metadata, which is useful but does not disclose other behavioral traits (e.g., pagination, rate limits, data freshness).

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 but contains redundancy: 'FREE. (FREE)' adds no value. The first sentence is efficient, but the repeated 'FREE' detracts from 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?

Given a simple list operation with one parameter and no output schema, the description is minimally adequate. It explains the core functionality and return content, but lacks details on potential limitations (e.g., total assets, performance) or output structure.

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% (parameter 'wallet' has a description). The tool description does not add any additional parameter semantics beyond that, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'List all assets in your wallet storage with sizes and metadata,' which clearly identifies the action (list) and resource (assets). It distinguishes itself from siblings like get_asset (single asset) and search_artworks (search across artworks).

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 usage guidance is provided. There is no indication of when to use this tool vs. alternatives like search_artworks or get_asset. The mention of 'FREE' is not contextual guidance.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating safe, read-only behavior. The description adds pricing details ('FREE. ($0.10 / 1 GCX)') but no other behavioral traits beyond those implied by the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single clear sentence followed by a brief cost note. All information is front-loaded and every word adds value with no 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 3 parameters, no output schema, and clear annotations, the description sufficiently explains the tool's purpose, products, and cost. No gaps are evident for correct invocation.

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?

Input schema covers all 3 parameters with descriptions (e.g., 'Base64-encoded design image', 'Product type', 'Background hex color'). The description adds no additional semantic meaning beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses a specific verb ('Place your design onto product mockups') and resource ('product mockups'), listing all product types. It clearly distinguishes from sibling tools like remove_background or resize_image, which serve different purposes.

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?

Description states the use case ('e-commerce and print-on-demand') and that it's free, providing clear context. However, it does not specify when not to use this tool or mention alternatives, though siblings offer no direct substitute.

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

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description does not need to reiterate safety. It adds 'FREE. (FREE)' as a cost note but does not disclose any other behavioral traits beyond what annotations provide. The description is consistent with annotations, no contradiction.

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 covers the main features, followed by a repetitive 'FREE. (FREE)'. This is efficient but slightly redundant. It is front-loaded and to the point.

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 8 parameters and no output schema, the description covers the core functionality but does not explain what the output is (e.g., returns the prepared image as base64 or a file). While the schema is rich, the description could be more complete by mentioning output format or limitations (e.g., max image size).

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 each parameter is already documented. The description repeats some information (e.g., supported sizes) but does not add new meaning beyond the schema. Per rules, baseline is 3, and the description does not exceed that.

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 prepares images for professional printing and lists specific features (DPI, bleed margins, crop marks) and supported sizes (A4, A3, Letter, poster, custom) and formats (TIFF, PDF). This distinguishes it from sibling tools like resize_image or remove_background, which serve different purposes.

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 printing preparation but does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it. No exclusions or alternatives are provided, leaving the agent to infer usage context from the features listed.

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

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

Annotations provide idempotentHint and non-destructiveHint; description adds cost and indexing method, with no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no fluff, includes cost and key technical details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks output description; agent cannot infer what the tool returns (e.g., hash ID or status), though annotations help.

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 the only parameter fully; description adds context about hash type but no additional parameter-level details.

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 registers a 256-bit perceptual hash with LSH band indexing for strip-proof provenance, distinguishing it from siblings like verify_provenance.

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 explicit guidance on when to use this tool versus alternatives like verify_provenance or enrich_metadata; only the purpose is implied.

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

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

Annotations indicate idempotentHint=true and destructiveHint=false, which are consistent with a registration operation. The description adds behavioral context beyond annotations by specifying that this gives free credits ($1 value) and that it is free, helping the agent understand the outcome and side effects.

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 extremely concise (two short sentences) and front-loads the key information: action, reward, and constraint. Every phrase adds value without redundancy, earning top marks.

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 simplicity (single parameter, no output schema) and the presence of informative annotations, the description adequately covers the essential context. It explains the credit reward and usage constraint, though it could briefly mention the expected result (e.g., wallet registered successfully) 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?

With 100% schema description coverage, the parameter 'wallet' is already documented as 'Your EVM wallet address (0x...)'. The description does not add further semantic meaning beyond what the schema provides, warranting the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states the tool registers a wallet to receive free credits, distinguishing it from other tools in the sibling list. The verb 'register' combined with the resource 'wallet' and the specific reward (10 FREE GCX credits) makes 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 clearly states the constraint 'New wallets only' and provides context about using the credits for upscale and enrich. However, it does not explicitly state when not to use this tool (e.g., returning users) or mention alternatives for obtaining credits, which would improve guidance.

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

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety profile is clear. Description adds model name (U2-Net) and output format but no additional behavioral traits like rate limits or auth needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences covering purpose, output, and use cases. The repeated 'FREE' is slightly redundant but does not harm clarity. Front-loaded with key information.

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 two-parameter tool with no output schema and supportive annotations, the description covers the main behavioral aspects (output format, use cases, free status). Lacks only minor details like image format restrictions for input (but schema covers base64).

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 clear descriptions for both parameters (image base64, output_format enum). The description does not add further meaning beyond what the schema provides, meeting the baseline but adding no extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action (remove background), technology (U2-Net), and output (RGBA PNG/WebP with transparency). Provides use cases (product photos, portraits, design assets) that distinguish it from sibling tools like resize_image or upscale_image.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly mentions ideal use cases (product photos, portraits, design assets) giving clear when-to-use guidance. Does not mention alternatives or when not to use, but sibling tool names imply other image 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which align with resizing being non-destructive. The description adds no behavioral contradictions. However, it includes the redundant 'FREE' note which is 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?

The description is fairly concise with two main sentences and a small redundancy (repeated 'FREE'). It is front-loaded with the core purpose. Minor waste, but still effective.

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?

There is no output schema, and the description does not explain the return value (e.g., base64 string or URL). It also lacks details on file size limits, performance, or handling of large images. Given the tool's complexity and missing output info, completeness is inadequate.

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 all parameters thoroughly. The description does not add additional meaning beyond the schema; it only restates modes. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action ('Resize an image to target dimensions') and lists specific modes. It also mentions use cases (thumbnails, social media) which distinguishes it from sibling tools like upscale_image or remove_background.

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 some context for when to use (preparing images for platforms), but does not explicitly state when not to use or mention alternatives among siblings. Usage is implied rather than 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?

Annotations already declare readOnlyHint=false (write), destructiveHint=false, idempotentHint=true. Description adds storage limits (100MB, 500 max) and cost, which are beyond annotations. No contradictions. However, it does not elaborate on behavioral traits like confirmation or error handling, and annotations carry most behavioral burden.

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?

Description is extremely concise: a single sentence plus a parenthetical cost note. No wasted words, all information is relevant and front-loaded. Every sentence 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?

Given 5 parameters, some optional with nested objects, and no output schema, the description covers the main function and constraints (limits, cost). However, it does not mention return values or confirmation, which would be helpful for a save operation. Adequate but could be more complete with expected output.

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 all 5 parameters described in the schema. The tool description does not add any additional meaning or context beyond what is already in the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Save an image or data to your personal wallet storage', specifying the verb 'save' and the resource 'image or data to personal wallet storage'. It includes constraints like 100MB free, 500 assets max, and cost, which further clarify the scope. Distinguishes from siblings like delete_asset, get_asset, and list_assets by being a write/storage 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?

Description implies usage for storing images or data to wallet storage with limits. It does not explicitly state when to use vs alternatives or when not to use, but the context of personal wallet storage and constraints provides clear usage context. No exclusions or alternatives are mentioned, though the sibling list suggests alternatives for other 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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that the service is free and lists museums, but does not provide deeper behavioral context beyond what annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no wasted words, though 'FREE' is repeated. Structure is front-loaded and efficient.

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 a simple search tool with full schema coverage and safety annotations, the description provides sufficient context. It could mention result format, but the absence is not critical.

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?

All three parameters are fully described in the input schema (100% coverage). The description adds no additional meaning beyond the schema; it merely repeats the museum list already covered by the museum parameter 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?

Clearly states the tool searches museum artworks from a specific set of major museums, distinguishing it from sibling tools like get_artwork or search_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 explicit when-to-use or alternatives are given, but the description implies it is for searching artworks across multiple museums, which is clear from context and sibling names.

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

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds 'FREE' and 'without loading all schemas' which aligns with annotations but does not provide additional behavioral detail beyond what annotations convey.

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?

Description is very short (one sentence plus parenthetical), concise and front-loaded. It conveys key information without unnecessary words, though it could include a hint about parameter usage.

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 search tool with 3 optional parameters and no output schema, the description is complete enough. Annotations cover safety concerns, and context signals confirm low 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?

Schema description coverage is 100%, so the schema already documents all parameters adequately. Description does not add parameter details, but baseline 3 is appropriate given full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the purpose: discover available tools by category or price without loading all schemas. It distinguishes from sibling tools like search_artworks and get_tool_schema by focusing on tools discovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly recommends starting here to save tokens, guiding the agent to use this tool first. Does not explicitly mention when not to use or alternatives, but provides clear context.

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

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

Annotations already indicate non-read-only, non-destructive, idempotent, and open-world. The description adds significant behavioral context: specific GPU hardware (L4), a cost of $0.20 per 2 GCX, and that five models are available. These details help the agent understand resource usage and constraints beyond what annotations provide.

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?

Extremely concise: two sentences covering purpose, models, default, and cost. Every sentence adds value. However, it could be slightly more structured (e.g., bullet points for model options) to improve scanability.

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?

Covers core functionality, models, default, and cost. Missing details: output format (assumes upscaled image), input size limits, explanation of 'GCX' credits, and behavior on failure. For a tool with no output schema and 3 parameters, this is adequate but not fully comprehensive.

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 detailed parameter descriptions, especially for the 'model' enum listing all options and defaults. The description adds 'Default: 2x general upscale' and mentions content types, but this largely repeats schema info. No additional syntax or constraints beyond 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 does super-resolution using Real-ESRGAN on an NVIDIA L4 GPU, lists 5 models for different content types, and specifies the default behavior (2x general upscale). This distinguishes it from sibling tools like resize_image which likely only resamples without AI enhancement.

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 explicit guidance on when to use this tool vs alternatives like resize_image or other upscaling tools. The description implies it's for quality upscaling but does not mention when not to use it, prerequisites, or alternative tools. An agent would need to infer usage from context.

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

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

Annotations already denote readOnlyHint=true and idempotentHint=true, so the burden on description is lower. The description adds that the tool returns raw SVG XML string, which is useful behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two sentences) and front-loaded with the main purpose. However, the redundant 'FREE. (FREE)' is unnecessary and slightly detracts from 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?

Given full schema coverage and annotations, the description adequately states output format (SVG XML string) and modes. Minor lack of details on input constraints or limitations, but overall sufficient 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?

Schema coverage is 100% with descriptions for all 4 parameters. The description summarizes modes and precision controls but adds no new meaning beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the action 'Convert raster images to SVG vector format' with the specific verb 'convert' and resource 'raster images to SVG', making it clear and distinct from sibling tools like resize_image or remove_background.

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 vectorization but lacks explicit guidance on when to use this tool versus alternatives (e.g., 'for vectorization, use this; for other image processing, see siblings'). No 'when to use' or 'when not to use' is 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?

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive traits. The description adds 'strip-proof' and 'free' but does not significantly extend behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but includes redundant repetition of 'FREE'. It is not optimally structured; the value is stated but could be more polished.

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 output schema, the description should hint at what the tool returns (e.g., verification result). It lacks this information, making it incomplete for an agent to fully understand the tool's usage.

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?

Parameter 'image' is already fully described in the schema (100% coverage). The description adds no additional semantics, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool verifies provenance using Aegis hash index, with a specific verb and resource. It distinguishes from sibling tools like get_artwork which retrieve data, while this tool verifies authenticity.

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 on when to use this tool versus alternatives. The description only mentions it is free, but does not explain context, prerequisites, or scenarios where verification is needed.

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

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

Annotations already declare readOnlyHint and idempotentHint, so the agent knows it's a safe read operation. The description adds that it returns the text payload, which is useful but limited.

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 informative sentences but includes redundant 'FREE. (FREE)' which wastes space. Could be 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?

Covers purpose and return value for a simple tool, but lacks guidance on when to use it versus the sibling watermark_embed tool. Adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear description for the single parameter. The tool description adds no additional detail 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 action (detect and extract) and the resource (invisible DCT watermark from an image), and specifies the output (embedded text payload). It distinguishes from sibling 'watermark_embed'.

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 explicit guidance on when to use this tool vs alternatives like 'watermark_embed'. The usage is implied but not 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?

The description reveals the watermark is invisible, uses DCT-domain, and survives light compression. However, it contradicts the 'readOnlyHint' annotation by describing a write operation. This contradiction reduces trust. Without annotations, it would better convey the modifying nature.

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 with two sentences. It front-loads the purpose and adds key details. However, the repetition of 'FREE' is unnecessary and slightly degrades quality. Overall efficient.

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 no output schema, so the description must clarify what the tool returns (e.g., base64-encoded watermarked image). It does not mention the return format or any post-processing steps. This is a significant gap for a 3-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description adds limited value. It mentions DCT-domain and luminance channel, which are technical details beyond the schema, but does not provide essential usage context for parameters like 'strength' beyond what the schema already describes. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: embedding an invisible DCT-domain watermark into an image. It specifies the encoding mechanism (luminance channel frequency coefficients) and a key property (survives light compression). This distinguishes it from the sibling 'watermark_detect' which detects watermarks.

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 mentions the tool is 'FREE' but provides no guidance on when to use it versus alternatives. It does not explicitly state prerequisites, exclusions, or compare with sibling tools. Usage context is implied for embedding watermarks but lacks explicit recommendations.

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