Get profile detail

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

Annotations already declare readOnlyHint=true, and the description is consistent. It adds valuable behavioral context by disclosing that cookie_data is omitted by default due to size, and that include_cookie controls this. This goes beyond the safety annotation and explains a key output trait.

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, no waste. The first sentence front-loads the core purpose and key included elements; the second adds an important conditional detail. Perfectly sized.

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 only 2 parameters, no output schema, and read-only annotations, this description fully covers what the tool returns and the key conditional behavior. No missing context for an agent to use it correctly.

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 100% with both parameters documented. The description enriches include_cookie by explaining why cookies are omitted (large size) and clarifies profile_uuid's role in fetching a profile's full config, providing rationale beyond the schema.

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 'Get the full configuration of a profile' with specific resources (fingerprint, proxy, folder), distinguishing it from sibling tools like list_profiles and get_fingerprint_options. It also explicitly notes the cookie omission behavior, which adds clarity.

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 this tool is for retrieving full profile configuration, while list_profiles likely provides summaries. It does not explicitly state when to use alternatives, but the context of 'full configuration' and the cookie omission note gives clear usage guidance.

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