list_solution_components

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

Annotations only declare readOnlyHint=true; the description adds real behavioral context beyond that — results are limited to *visible* rows, no code/XML/configuration is read, and row completeness is not evidence of export payload contents. It does not mention pagination/defaults or permission requirements, keeping it out of 5 territory.

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?

Three tight sentences, front-loaded with the core action and followed by constraints. Dense to the point of being elliptical ('root inclusion behavior are separate'), but nothing is wasted.

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?

No output schema and nine schema properties mean the description should carry more weight than it does: it never explains the returned row shape beyond naming objectid/type and row ID, does not note that at least one solution-name form is required, and does not clarify the maxPages/alias behavior. Adequate for a read-only list tool, but with gaps an agent would hit.

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 56%, with top, maxPages and componentId documented but componentType and the solution name parameters undocumented. The description partially compensates by warning that objectid, membership row ID and root inclusion are separate concepts (reinforcing the schema's 'NOT the membership row GUID' note) and that filters combine with the solution, but it never mentions the anyOf requirement for a solution name or the alias pairs.

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 a specific verb and resource with scope: list *visible solutioncomponent membership rows* for an *exact* solution. That clearly separates it from add_solution_component, get_solution_component_dependencies and list_solutions. The trailing clause about objectid/type, membership row ID and root inclusion behavior is cryptic rather than clarifying, so it stops short of a 5.

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?

'Optional filters combine with the solution' and the caveat that completeness does not prove export payload contents imply when the tool is useful (inventory before export), but no sibling is named and no explicit when-not guidance is given. Usage must be inferred from the sibling list.

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