List Schemas

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

With no annotations, the description carries the burden. It discloses that results are filtered by access policy and user-specific, which is helpful. However, it does not explicitly state it's read-only or describe potential edge cases (e.g., empty results). Behavioral transparency is adequate for a simple list tool but could be improved.

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, which is concise, but it sacrifices completeness. It could be restructured to front-load key info and include parameter details. The conciseness feels like under-specification rather than efficiency.

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?

For a simple tool with one parameter and no output schema, the description should at minimum explain the parameter's role. It fails to do so, leaving the agent to guess about 'profile'. Contextually incomplete for reliable invocation.

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 single parameter 'profile' has no description in the schema (0% coverage) and is not mentioned in the tool description. The description does not explain what profile is, whether it's required, or how it affects results. This is a significant gap.

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 uses specific verb 'List' and resource 'schemas/databases', and adds context about visibility to current user and filtering by access policy. This clearly distinguishes it from sibling tools like ob_list_tables or ob_list_profiles.

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?

No guidance on when to use this tool versus alternatives (e.g., ob_search_catalog). No mention of prerequisites or scenarios. The description only states what it does, not when to invoke it.

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