database_get_schema

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

No annotations, and the description only says 'get' without mentioning side effects, error conditions, connection requirements, or return structure. Lacks behavioral detail expected for a tool with zero annotation support.

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?

Single sentence that directly states the tool's function. No repetition or unnecessary qualifiers.

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 read-only tool with one optional parameter, the description adequately enumerates the returned metadata types. Could mention default schema behavior or connection dependency, but the parameter description covers the default aspect.

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 only parameter 'schema' is fully described in the input schema (100% coverage). The description adds no extra semantic detail beyond what the schema already provides.

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?

Says 'Get the database schema' with a specific list of schema elements (tables, columns, indexes, foreign keys, views). Clearly distinguishes from execute-style sibling tools.

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 explicit use-case guidance or comparison to alternatives. However, the purpose is clear enough that usage is implied; not misleading.

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