list_ip_cores

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists IP cores with optional filtering, but doesn't describe what 'list' entails (e.g., format, pagination, or limitations), whether it's read-only or has side effects, or any performance or access considerations. This leaves significant gaps for a tool with no annotation coverage.

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

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

The description is a single, efficient sentence that front-loads the core purpose ('List all available IP cores in the registry') and adds a useful detail ('Optionally filter by category'). There is no wasted text, and it's appropriately sized for a simple tool with one optional 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?

Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and parameter intent, but lacks details on behavior, output format, or usage context. For a list tool with no annotations, it should ideally explain more about what 'list' returns or any limitations.

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 description mentions optional filtering by category, which aligns with the single parameter in the input schema. Since schema description coverage is 100% (the parameter is fully documented in the schema), the description adds minimal value beyond what's already structured. It doesn't provide additional syntax, examples, or constraints, so it meets the baseline for high 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 clearly states the verb ('List') and resource ('all available IP cores in the registry'), making the purpose specific and understandable. It distinguishes from siblings like 'get_ip_core' (singular retrieval) and 'search_github_cores' (external search), though it doesn't explicitly mention these alternatives. The optional filtering adds useful scope but doesn't fully differentiate from all siblings.

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 listing IP cores with optional filtering, but provides no explicit guidance on when to use this tool versus alternatives like 'get_ip_core' (for single core details) or 'search_github_cores' (for external repositories). It mentions filtering by category, which gives some context, but lacks clear when/when-not instructions or prerequisites.

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