deepseek_profiles

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

No annotations are provided, so the description carries the full burden. It reveals a key behavioral trait: the tool returns sanitized data and 'Never returns API keys, base URLs, or headers.' This is a meaningful safety guarantee. It doesn't discuss error handling or auth, but for a simple read-only listing tool, this suffices.

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 two sentences, with the primary action front-loaded. Every word adds value: 'sanitized' sets expectations, 'providers and model ids' specifies output, and the second sentence clarifies exclusions. No redundancy or filler.

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-only tool with no parameters and no output schema, the description fully covers what the agent needs to know: the output content (providers and model ids) and safety guarantees (no secrets returned). The sibling tool names provide context that this is a support tool for run management, so completeness is adequate.

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 tool has zero parameters and the schema coverage is 100% (empty object). With no parameters to explain, the baseline for zero params is 4. The description does not need to compensate for parameter details.

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 function with a specific verb ('List') and resource ('sanitized Claude Code Haha providers and model ids'). It also adds a safety qualifier ('sanitized') and explicitly what it never returns. This distinguishes it from the sibling tools (status, start, wait, cancel, run), which are action-oriented.

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 does not explicitly state when to use this tool versus alternatives. However, the verb 'List' and the resource 'providers and model ids' imply it is for retrieving profile information, contrasting with the action-oriented sibling names. No exclusions or alternative guidance is provided, so it's implied rather than explicit.

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