get_component_by_slug

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

No annotations are provided, so the description carries the full burden. 'Retrieve' reasonably conveys a read-only, non-destructive lookup, but nothing is said about behavior on a missing or malformed slug, or what 'exact details' encompasses.

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 front-loaded sentence with no wasted words. It is efficient, though arguably too terse for a tool that could use a clause on the return or error behavior.

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

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

For a single-parameter lookup with a fully documented schema and no output schema, the description covers the essential identity of the tool. It still leaves gaps on return shape and failure behavior that an agent calling it blind would want.

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 slug property already documents the 'shopId:itemId' format with an example. The description's phrase 'composite slug' reinforces that without adding format or validation detail beyond the schema, so the baseline 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?

States a specific verb (Retrieve) and resource (component details) and qualifies it as an exact lookup by composite slug, which hints at the distinction from search_components. It does not explicitly differentiate from get_component_by_id, so an agent must infer the ID-vs-slug split from the parameter name.

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?

Usage is only implied: 'using a composite slug' suggests calling it when a slug is in hand, but there is no explicit when-to-use, when-not-to-use, or pointer to search_components/get_component_by_id as alternatives.

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