agent_catalog_detail

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

Despite no annotations, the description discloses key behaviors: it is read-only (READ), public authentication, small response (~2KB), and returns parameter hints, auth requirements, and workflow. This is sufficient for an agent to understand the tool's impact and safety.

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-organized with clear headings, front-loaded with a summary, and each section provides necessary information without redundancy. Every sentence adds value, making it easy for an agent to parse.

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 simple input (one parameter) and no output schema, the description covers all necessary aspects: purpose, usage scenario, parameters, authentication, risk, response size, and workflow. It is complete for an agent to use this tool effectively.

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 already provides a description and possible values for the domain parameter. The tool description adds context by listing values in a structured format and linking the parameter to the catalog workflow. Although there is slight inconsistency in values, it adds meaningful guidance 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 function: viewing a detailed tool list for a specific business domain, including parameter hints, authentication requirements, and recommended call order. This distinguishes it from sibling tools that provide actual data or execute trades.

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 explicitly specifies the usage context: after using agent_catalog to select a domain, call this tool to get detailed information. It also outlines the intended workflow: agent_catalog -> this tool -> direct target tool call, providing clear guidance on when to use it vs. alternatives.

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