List Oracle Objects

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

No annotations are provided, so the description carries full burden. It states the tool returns 'policy-filtered' metadata but does not disclose permissions, rate limits, side effects, or whether the listing is live or cached. Minimal behavioral context beyond the basic action.

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 a single sentence, making it concise, but it is overly minimal. It could include additional context (e.g., filtering behavior, output format) without becoming verbose.

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 5 parameters with no schema descriptions, no output schema, and no annotations, the description is incomplete. It does not explain how the tool filters, what the output contains, or any constraints (e.g., maximum limit). A more detailed description is needed.

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 description coverage is 0%. The description does not explain any of the 5 parameters (limit, query, schema, profile, objectTypes), leaving the agent with no semantic guidance beyond the schema structure. The list of example object types is insufficient.

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 action ('list') and the resource ('policy-filtered Oracle object metadata'), listing specific object types like views, sequences, synonyms, procedures, functions, and packages. This distinguishes it from sibling tools such as ob_list_tables or ob_get_object_metadata.

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 when listing metadata for certain object types but provides no explicit guidance on when to use this tool over alternatives like ob_list_tables or ob_search_catalog. No exclusions or scenarios are mentioned.

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