list_resources

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

The description discloses key behavioral traits: 'Works offline from a bundled seed list' and 'Filter by search and/or module.' Since no annotations are provided, the description carries the full burden. It could mention the limit parameter and pagination behavior, but the offline nature is critical and well-stated.

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 concise: two sentences plus a succinct list of parameters. It is front-loaded with the primary action, and every sentence adds value—purpose, offline behavior, filtering, and next-step guidance. No wasted words.

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 tool's moderate complexity, an output schema exists, so return values need not be detailed. The description covers the core functionality, offline behavior, filtering, and suggests a follow-up tool. It lacks mention of the limit parameter and pagination, but these are minor omissions for a search-catalog 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?

With 0% schema description coverage, the description adds meaning for two of three parameters: 'search (matches name/title/description)' and 'module (e.g. core_hr, ...).' The limit parameter is not explained, but it has a default and is optional. The examples for module are helpful.

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 purpose: 'Search the catalog of common Oracle Fusion HCM REST resources.' It distinguishes itself from siblings like describe_resource by noting that it works offline from a bundled seed list, making its scope and method explicit.

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 guides when to use this tool versus an alternative: 'Use describe_resource to confirm a resource's live schema.' This tells the agent that list_resources is for initial discovery from an offline catalog, while describe_resource provides live schema details. It implies that list_resources should be used before describe_resource and not for actual data retrieval.

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