list_solutions

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

No annotations are present, so the description carries the full burden. It only says 'list', implying a read operation, but fails to disclose important behaviors like the default exclusion of managed solutions (which is only in the schema) or any pagination/ordering. For a tool with no annotation support, this is a significant gap.

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 very brief, which is good for conciseness, but the parenthetical 'uniquename is used to filter list_entities' is a confusing aside that doesn't directly relate to listing solutions. It reads like a fragment or cross-reference that could be better placed in the description of list_entities.

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?

With no output schema and minimal description, the agent has no idea what the response looks like or what fields are returned. The reference to uniquename without explanation adds ambiguity, and the tool description fails to describe the solution entity's key properties, making it incomplete for a listing tool.

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 covers the single optional parameter include_managed with a clear description (default false, only unmanaged returned). The tool description adds no additional parameter semantics, so the baseline 3 applies given the high schema coverage.

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 tool 'List Dataverse solutions' with a specific verb and resource. However, the parenthetical 'uniquename is used to filter list_entities' introduces a tangential reference to another tool, which could confuse the primary purpose. Despite this, the main action remains unambiguous.

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 provides a cross-tool hint: if you need to filter entities, use list_entities with uniquename. This implies an alternative usage, but it doesn't explicitly state when to use list_solutions itself, such as when you need an overview of all solutions or to find a solution's uniquename.

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