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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is well-covered. The description adds meaningful behavioral context: it specifies that the status is from a frozen vocabulary, includes an effective date and rule-set version, and references a source page. This goes beyond the annotations and helps the agent understand the nature of the returned data without needing to inspect the output schema. The only minor gap is that it doesn't describe the exact structure of the response, but that is covered by the output schema.

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 one clear, dense sentence that front-loads the core data (status with frozen vocabulary) and then lists the associated metadata (effective date, rule-set version, source page). No filler words; every element contributes meaning. It is appropriately sized for a tool of this simplicity.

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?

The tool has a fairly simple signature (3 params, no nested objects) and an output schema exists, so the description doesn't need to explain return structure. It covers the essential context: what the status represents, that it is jurisdiction- and pathway-specific, and that it includes metadata. Given the annotations already cover safety and idempotency, the description is sufficiently complete for an agent to invoke it correctly. The only missing piece is explicit guidance on choosing this over similar lookups like get_substance_record, but that is a minor gap given the clarity of the resource.

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 schema has 0% description coverage, meaning neither the properties nor the description explain the parameters. The description mentions 'substance', 'pathway', and 'jurisdiction' implicitly but doesn't add format, enumeration, or selection guidance. However, the parameter names themselves are fairly self-explanatory, and the description's reference to 'one pathway in one jurisdiction' clarifies the semantic scope. Since the description adds marginal value beyond the parameter names but doesn't fully explain constraints (e.g., frozen vocabulary for status, not for substances), a baseline 3 is appropriate.

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 the specific resource (substance, pathway, jurisdiction) and the kind of data returned (status with frozen vocabulary, effective date, rule-set version, source page). It clearly distinguishes this from sibling tools like compare_presentations or get_item, though it doesn't explicitly name a sibling as an alternative. The verb is implicit ('The status of...') but the resource and output are specific enough for an agent to understand the purpose.

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 when to use this tool (when you need the status of a substance on a specific pathway in a specific jurisdiction with frozen vocabulary). It does not explicitly state when not to use it or mention alternatives like get_substance_record or compare_presentations. The context of sibling tools suggests this is a targeted lookup, but no explicit exclusions are given, leaving the agent to infer the scope.

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