browse_category

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

With no annotations, the description bears full responsibility for behavioral traits. It discloses defaults (limit 50, system icd10cm) and maximum limit (100), which is helpful, but does not explicitly state read-only behavior or side effects. The tool name 'browse' implies read-only, but not explicit.

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 concise and well-structured: a single-sentence purpose followed by clearly formatted parameter bullet points. Every sentence is useful, and the most critical information (purpose, prefix, system, limit) is front-loaded.

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 presence of an output schema (not shown), the description need not explain return values. It covers the core purpose, all parameters with defaults and constraints, and differentiates from siblings implicitly. The description is complete for a straightforward browsing tool.

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 0% (no property descriptions in schema), so the description must compensate. It provides detailed semantics: prefix examples ('E11', 'I25'), system values ('icd10cm', 'icd9cm', 'icd10who'), limit default (50) and max (100). This adds significant 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?

The description clearly states the tool's purpose: 'Browse all codes under a category prefix.' The verb 'browse' and resource 'codes under a category prefix' are specific and distinct from sibling tools like lookup_code (single code) and search_codes (query), making it easy for an AI agent to select correctly.

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 through parameter explanations but does not explicitly state when to use this tool over alternatives. No when-not or where-else guidance is provided, so the agent must infer context.

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