List profiles

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context beyond the annotations by noting that running state is omitted and that pagination/search are supported. However, it doesn't describe the response envelope or any rate limiting, which would be additional value.

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 sentences, front-loaded with the core purpose and a key differentiator. No wasted words; every phrase earns its place.

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?

For a list operation with no output schema, the description clearly states the resource, the filtering/search capabilities, and the important exclusion of running state. It could have mentioned the structure of the paginated response (e.g., whether it returns a total count), but the core behavior is adequately covered given the annotations.

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 description coverage is 67%, with page, keyword, page_size, and folder_uuid already described in the schema. The description adds the context of pagination and search but does not clarify the meaning of sort_by or sort_order, which lack schema descriptions. Since the description doesn't compensate for the undocumented parameters, it only meets the baseline.

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 it lists browser profiles with pagination and search, immediately distinguishing it from list_running_browsers by explicitly noting running state is excluded. The verb 'list' and resource 'browser profiles' are specific and 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 explicitly tells the agent when not to use this tool: 'running state is not part of this list — use list_running_browsers for that.' This names the alternative tool directly and provides clear exclusion criteria, making usage guidance strong.

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