smartscout_system_info

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

With no annotations, the description carries the full behavioral burden. It implies a safe metadata read but never states side-effect profile, auth requirements, or that results are static schema metadata rather than live data. It does at least signal the return content ('databases and their schemas'), which is the one behavioral hint present.

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?

A single front-loaded sentence with no filler, appropriate for a simple introspection tool. It could carry slightly more routing information without becoming bloated, but nothing is wasted.

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 one-parameter, optional-argument metadata tool with no output schema, the description is minimally adequate: it conveys what the tool surfaces but not how it differs from the several sibling dataset-listing tools. An agent could call it correctly but might pick a sibling by mistake.

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 100%, so the single optional enum parameter is already fully documented. The description's phrase 'available SmartScout databases' loosely frames the parameter but adds no format or filtering detail beyond the schema, which is the expected baseline when the schema does the work.

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?

States a specific verb (Get) and resource (information about SmartScout databases and their schemas), which is distinct from the catalog/product/brand/keyword focus of siblings. It does not, however, distinguish itself from near-neighbors like smartscout_list_datasets or smartscout_check_datasets, leaving some ambiguity about which introspection tool to pick.

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 call this versus list_datasets, check_datasets, or dataset_status, all of which sound like related discovery tools. There is no mention that this is a discovery/introspection call that might logically precede a smartscout_custom_query.

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