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 value by stating it does not write local files and that using assetType avoids large payloads. No contradictions. It provides optimization guidance beyond the safety profile.

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 with zero waste. First sentence states the core action and key constraint (no file writes). Second sentence provides critical parameter guidance. Perfectly front-loaded and every word 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 an output schema exists (not shown but noted), the description need not explain return values. It covers purpose, usage guidelines, parameter optimization, and behavioral constraints. With 4 parameters and high schema coverage, it is sufficiently complete for an agent to use 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?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining assetType enumeration values (e.g., 'install_command', 'config_snippet') and the rationale for using it to reduce payload size. This extra context elevates the score above baseline.

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 fetches a category-aware copy/install asset for a HeyClaude entry without writing local files. It distinguishes from sibling tools (e.g., registry, install, and other entry tools) by focusing on asset retrieval. The verb 'Fetch' with specific resource 'asset' is precise.

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 'without writing local files' and advises using assetType to avoid unnecessary payloads. It implies when to use this tool over others (e.g., when you need only a specific asset type), but does not explicitly name sibling alternatives. The guidance is clear and context-specific.

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