describe_instance_linked_whitelist_template

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

The description adds no behavioral details beyond what the 'readOnlyHint' annotation already conveys. It does not mention any side effects, authentication requirements, performance implications, or limitations such as the scope of the template.

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 minimal but lacks substance. Conciseness is achieved at the expense of utility, with no meaningful information beyond a placeholder structure.

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 no output schema and no parameter descriptions, the tool is completely underspecified. The agent cannot determine what the tool does or what a successful response looks like.

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 only lists the parameter names ('region_id', 'db_instance_id') without explaining their purpose, valid values, or format. The agent cannot infer what these parameters mean.

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 merely restates the tool name as 'describe instance linked whitelist template' without clarifying what a whitelist template is or what specific information is returned. This is a tautology, as it uses the same words as the name.

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 is provided on when to use this tool versus sibling tools like 'describe_all_whitelist_template' or 'attach_whitelist_template_to_instance'. There is no context for appropriate usage.

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