get_collection

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'Read-only' merely restates that. It does add value by disclosing the returned contents (member products, per-channel sync status), but says nothing about permissions, whether a missing uuid errors versus returns empty, or freshness of the sync data.

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 short sentences with the scope and payload front-loaded, no filler. Slightly marred by the stray trailing artifact '[#71cbae]' that carries no meaning for an agent.

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 does reasonably well by enumerating the return contents, and annotations cover the safety profile. However, three undocumented parameters, including two required uuids, and no guidance on the workspace scoping leave it short of 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 description coverage is 0% across three parameters. The description only gestures at 'by uuid' and never addresses the distinction between store_uuid and collection_uuid, both required, nor what the optional 'workspace' parameter does. It fails to compensate for the coverage gap.

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 and resource ('Get a single collection by uuid') and goes further to name what the payload contains (member products, per-channel sync status). It is implicitly distinguished from the sibling list_collections by 'single', though it never names the alternative explicitly.

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 implied: 'by uuid' tells the agent this is the direct-lookup path versus a list tool, but there is no explicit when-to-use, no prerequisite statement, and no named alternative such as list_collections or sync_collection.

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