get_instance

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

With no annotations, the description carries the burden of behavioral disclosure. 'Get' signals a read-only retrieval, 'summary' indicates a limited return shape, and 'Defaults to the current instance' reveals the omitted-parameter behavior. It does not cover no-match errors or permissions, but those are less critical for a simple getter.

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?

Two short sentences with no filler. The core action and the key default behavior are front-loaded, making the description easy to parse quickly.

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 low complexity—one optional parameter, no nested objects, no output schema—the description covers the essential invocation and default behavior. The return value is only described as a 'summary', but that is likely adequate for this tool. A brief pointer to list_instances or use_instance would make it fully complete.

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 schema already documents the single 'name' parameter with 100% coverage, so the baseline is 3. The description adds meaning beyond the schema by specifying the default behavior when the parameter is omitted: it uses the current instance.

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 the action ('Get'), the resource ('a summary of one CurseForge instance'), and adds the useful default behavior. It distinguishes itself from list_instances by focusing on a single instance rather than a collection.

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?

The description implies a single-instance use case and explains the current-instance fallback, but it never explicitly mentions alternatives like list_instances or use_instance. The guidance is inferred rather than stated.

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