openpanel_get_instance_info

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

No annotations provided, so description carries full burden. States it retrieves information implying read-only behavior, but fails to disclose side effects, authentication requirements, rate limits, or response structure.

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 is efficient, but '[UNIFIED]' prefix appears to be internal metadata noise that doesn't aid selection. Structure is front-loaded but damaged by the bracketed prefix.

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 single-parameter tool, fails to document the required 'site' parameter. Mentions return values (URL and configuration) but without output schema, parameter documentation was critical and missing.

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% with one required parameter 'site' completely undocumented. Description fails to compensate by explaining what 'site' represents (ID, URL, domain?) or its expected format.

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 specific verb (Get) and resource (OpenPanel instance information), mentioning included fields (URL and configuration). Distinguishes implicitly from project-specific siblings like openpanel_get_project, though lacks explicit 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?

Provides no guidance on when to use this versus other OpenPanel information-retrieval tools (e.g., openpanel_get_project or openpanel_get_dashboard). No conditions or prerequisites mentioned.

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