Retrieve database

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

Annotations already declare readOnlyHint and idempotentHint, which cover safety. The description adds the behavioral detail that the tool discovers child data source IDs, but it does not disclose any side effects, permissions, or potential limitations. The output schema further reduces the need to explain return values, so a score of 3 reflects the marginal added context beyond annotations.

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, focused sentence that conveys the essential function without any unnecessary words. It front-loads the verb and resource, achieving high conciseness.

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 one-parameter tool with read-only annotations and an output schema, the description sufficiently covers the purpose and key outputs. It lacks explicit usage guidance relative to siblings, but given the tool's straightforward scope, the description is mostly complete.

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%, and the description does not elaborate on the databaseId parameter's format or semantics beyond the implicit implication from the tool name. It offers no additional parameter-level meaning, leaving the schema to stand alone without compensation.

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 uses the specific verb 'Retrieve' and identifies the resource as 'database container' while adding the unique discovery aspect of 'child data source IDs'. This clearly distinguishes it from sibling tools like get_page or query_data_source, making its purpose unambiguous.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention any alternatives, exclusions, or preconditions, making it purely descriptive without contextual direction for an AI agent deciding between tools.

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