Search PGS scores

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

Adds details beyond annotations: case-insensitive substring match across fields, genome build filter with specific builds mentioned, and limit on matches. No contradictions.

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?

Four sentences, all essential, with no wasted words. Purpose is front-loaded, followed by details on matching, filtering, and output.

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?

Covers search behavior, case sensitivity, fields, filter, limit. Output schema exists for return values, so missing ordering or pagination is minor. Adequate for a search 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 has 0% description coverage, but the description adds meaning: query is free text, genome_build is optional with specific build names, limit caps results. Adds value beyond raw 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 states 'Search the PGS Catalog for polygenic scores by free text' with a specific verb and resource, and distinguishes from sibling 'search_traits' by focusing on scores.

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 for free-text searching of polygenic scores but does not explicitly mention when to use this over alternatives like search_traits or when not to use.

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