Browse PhilPapers Taxonomy

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

With no annotations, the description carries the full burden. It discloses key behavioral traits: the hierarchy is a cached snapshot from a Cloudflare-blocked API, query overrides category_id, and category_id is optional. It also notes the semantic lens is inferred, not authoritative. It could add more detail about output structure, but the core behavior is clearly communicated.

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 well-structured and front-loaded, with the most important information in the first sentence. Every sentence adds value: the cache caveat, parameter usage, sibling tool integration, and a clarifying note about authority. No waste or redundancy.

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 there is no output schema or annotations, the description does a solid job explaining the tool's operation and limitations. It covers the two browsing modes (top-level and subcategories) and search behavior. It doesn't explicitly describe the return format, but for a simple category listing tool, the description is sufficiently complete for an agent to select and invoke it correctly.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the interplay of parameters: omitting category_id yields top-level areas, passing it lists subcategories, and query overrides category_id. This provides practical usage context not present in the raw schema properties.

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 function: 'Browse the expert-curated PhilPapers category hierarchy.' It specifies the resource (categories) and the action (browse), and differentiates from siblings like category_papers, search_papers, and get_related by explicitly showing how category_id can be used with those tools, but this tool itself is for listing categories.

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 provides explicit usage guidance: 'Omit category_id for the top-level areas; pass category_id to list its subcategories; pass query to find categories by name.' It also explains how to leverage the result with sibling tools ('call category_papers... or pass it as the category_id param to search_papers / get_related'), including a caveat about the inferred semantic lens. This clearly distinguishes when to use this tool versus alternatives.

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