Canada Drug Product Lookup MCP

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

No annotations are present, so the description carries the full disclosure burden. The 'PRO' prefix hints at a paid/subscriber tier (consistent with the access_token param), but there is no mention of auth failure behavior, rate limits, partial-failure semantics for a batch of up to 50, or whether the call is read-only.

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?

A single compact sentence with the batch limit and payload fields front-loaded; nothing is wasted. The opaque 'PRO.' prefix is the only element that does not clearly earn 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?

With no output schema, the description usefully names the three returned fields, but a batch tool of this shape should also cover partial results and the subscriber/access requirement. Adequate for a simple read-style lookup, incomplete around failure modes.

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 50%: access_token is documented in the schema as the subscriber token from /success or a Bearer header. The description adds the cardinality limit of 50 to the otherwise undocumented 'dins' array, which is genuine value 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?

States a specific verb and resource ('Check ... DINs') and enumerates the returned fields (brand, company, marketing status), so an agent knows exactly what it gets. It does not distinguish itself from the sibling din_profile, so it stops short of a 5.

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 'up to 50 DINs' phrasing implies a batched use case, but the description never says when to choose this over din_profile or drug_search, nor what happens with invalid or over-limit DINs. Sibling routing is left entirely to inference.

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?

With no annotations, the description carries the full burden. It usefully enumerates the returned profile fields and implies a read-style lookup, but it does not explicitly state read-only behavior, authorization requirements, error behavior, or what 'PRO.' means.

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 compact single sentence that efficiently lists the main profile contents. The leading 'PRO.' is cryptic and slightly reduces front-loading quality, but there is no wasted text.

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 lookup with no output schema, the description gives a useful content overview. It still leaves gaps around DIN format, explicit read-only/auth behavior, and the meaning of 'PRO.', so it is 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 only 50%, and the 'din' parameter has no schema description. The tool description says only 'for a DIN' and does not explain the DIN format or requirements; the access_token parameter is documented in the schema but not elaborated in the 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?

The description states a clear resource and content set: a full profile for a DIN including ingredients, strengths, status, schedule, route, dosage form, and ATC class. It does not distinguish this tool from siblings such as drug_search or batch_din_check, so it falls short of a 5.

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?

Use is implied by 'Full profile for a DIN' when an agent already has a DIN and needs comprehensive details. However, there is no explicit when-to-use guidance, no exclusions, and no comparison to the sibling tools.

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?

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool is free and returns only the top 5 results, but it does not explain result ordering, matching behavior, or return format.

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 and front-loaded, with cost and result-limit information placed clearly. The parenthetical '(DIN, company, class)' is slightly cryptic but does not bloat the description.

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 one-parameter search tool with no output schema and no annotations, the description covers purpose, cost, and result limit. It still leaves open what fields are returned and how matches are determined.

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%, so the description should clarify the single parameter. It only repeats 'brand name' without explaining exact vs. partial matching, format expectations, or how brand strings are interpreted.

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 ('Find') and resource ('Canadian drug products') and scopes it to brand-name lookup. It does not explicitly distinguish itself from siblings like din_profile or batch_din_check, but the brand-based search purpose is clear.

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 searching by brand name, but gives no explicit guidance on when to choose this over din_profile or batch_din_check. There are no exclusions or alternative-routing instructions.

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