get_instance_info

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and variability. The description adds specific return fields (base_url, edition, version, compat_reference, unavailable_features) and the behavioral benefit of avoiding 404 errors, enriching transparency beyond annotations.

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 brief and well-structured: purpose sentence, usage guideline, and return format. It is front-loaded with the core action. Could be slightly trimmed in the return dict list, but overall efficient.

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 the tool's simplicity (no params, has output schema), the description fully covers what the tool does, why to use it, and what it returns. It is self-contained and leaves no gaps.

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?

There are 0 parameters, so baseline is 4. The description adds no parameter info because none exist, but it is not expected to. It correctly focuses on the tool's output and purpose.

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 clearly states 'Get edition/version info and known API limitations of the connected Plane instance.' It uses a specific verb ('Get') and resource ('edition/version info and known API limitations'), distinguishing it from siblings that operate on projects, work items, etc.

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?

It explicitly advises to 'Use this to understand up-front which tool families are unavailable... instead of discovering them through 404 errors.' This provides a clear when-to-use and a rationale for using before other tools, with no ambiguity.

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