list_apis

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

No annotations provided, so description carries full burden. Discloses that order APIs are conditionally displayed based on server mode, which is useful. Does not mention read-only nature, error handling, or response format, but for a listing endpoint this is adequate.

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?

Three sentences with no redundancy. Front-loaded with purpose, then filtering options, then workflow advice. Every sentence adds value.

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?

No output schema exists, but description does not mention what the response contains (expected list of endpoints). However, the workflow with sibling tools (describe_api, call_api) provides implicit context. Adequate for a simple listing tool, but could be more explicit about return structure.

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 covers all 3 parameters (100% coverage). Description adds context: explains domain as asset class filter, keyword as partial match on summary/operationId/path, and category as partial match. This clarifies the matching behavior beyond the schema descriptions.

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 it lists available API endpoints from NH Investment & Securities Open API, specifies filtering dimensions (domain, category, keyword), and explicitly distinguishes it from sibling tools by outlining the workflow: use this to find operationId, then invoke describe_api or call_api.

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?

Explicitly advises using this tool first to locate operationId before calling describe_api/call_api. Also notes that order/trade APIs are only shown when server is in trade active mode. Does not explicitly state when not to use, but the sequential guidance is clear.

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