list_managed_hub_profiles

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

The description accurately reflects the read-only nature (list operation) consistent with annotations (readOnlyHint=true, destructiveHint=false). It adds clarity about the role filter, which is a behavioral aspect, and does not contradict 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 extremely concise, consisting of two short sentences. It delivers all necessary information without any unnecessary words or repetition.

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 large number of similar sibling tools, the description effectively differentiates this tool by specifying the role constraint. It also provides essential guidance for the parameter. Minor omission: it doesn't describe the return format, but this is not critical for a list operation.

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 single parameter workspace_id is fully explained in the description, including how to retrieve valid values. This adds meaningful context beyond the schema's basic type and title, making parameter usage clear.

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's purpose: listing hub profiles where the current user has Admin or Editor role. This specific scope distinguishes it from similar sibling tools like list_hub_profiles or filter_hub_profiles.

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 direct instruction for the required parameter (workspace_id) and tells the user to obtain it from list_workspaces(). While it doesn't explicitly contrast with all alternative listing tools, the role-filter context implies when this tool is appropriate.

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