get_all_hpo_terms

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

With no annotations, the description carries full burden. It discloses pagination behavior but omits details on whether the tool is read-only, potential large data volume, rate limits, or idempotency. The mention of 'all terms' implies a broad scope but lacks safety or behavioral cues.

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 concise single sentence covering purpose and key feature. No wasted words, but could include more useful details without becoming verbose. Slightly under-specified for a tool with no annotations or output schema.

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 complexity (list of all terms with pagination) and no output schema, the description lacks completeness. It does not mention return format, field structure, or behavior when paginated (e.g., order, total count). Sibling tools exist but no comparative context.

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 100%, so baseline is 3. The description adds no additional meaning beyond the schema; 'pagination support' is already evident from the max and offset parameters. Does not explain default values or ordering.

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?

Description clearly states 'Get a list of all HPO terms with pagination support', specifying the verb (get), resource (all HPO terms), and key feature (pagination). This distinguishes it from siblings like get_hpo_term (single term) and search_hpo_terms (filtered).

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 mentions pagination but provides no explicit guidance on when to use this tool versus alternatives like batch_get_hpo_terms or search. It lacks context on when pagination is necessary or recommended, and does not state when not to use it.

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