query_database

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

No annotations exist, so description must provide behavioral context. It states 'query' but does not confirm read-only nature, discuss side effects, error behavior, or rate limits. Minimal transparency.

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?

Short and front-loaded with purpose. Examples are helpful but could be more compact or integrated. Efficient use of space, though lacks structure for other parameters.

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 and an output schema, description misses return behavior, error handling, and parameter constraints. Incomplete for a complex query 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?

Schema coverage is 0%, so description must document parameters. Only filters are explained with examples, but syntax (e.g., operators, JSON structure) is incomplete. Other parameters (sort_by, sort_order, limit, database_id_or_url) receive no explanation.

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 the tool queries a database with filters and sorting. However, it does not distinguish from sibling tools like get_recent_pages or get_today_tasks, which also retrieve database content. The purpose is clear but lacks differentiation.

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. Agent must infer from context or trial and error. Examples only filter syntax, not usage scenarios.

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