think-with-deepseek-r1

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

No annotations provided. Description does not disclose any behavioral traits such as side effects, authentication needs, rate limits, or what 'Enhanced thinking' entails. Critical information is missing.

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?

Description is very short but includes some structure (Arg/Return). However, the phrasing is awkward and lacks clarity, making it less effective than a concise, clear statement.

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 no output schema and no annotations, description should cover more context. It neglects to explain 'Enhanced thinking', any prerequisites, or return format. Incomplete for a 1-param tool.

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 has one parameter 'prompt' with no description. Description adds 'user's full prompt (full text)', clarifying that input should be the complete prompt. This adds value beyond the schema but does not fully compensate for 0% schema coverage.

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?

Description states tool takes a prompt and returns enhanced thinking, but phrasing 'Ask deepseek-R1 for user's prompt' is ambiguous. It could be misinterpreted as fetching a prompt rather than processing one. Purpose is somewhat clear but not precise.

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?

No guidance on when to use this tool versus alternatives. No sibling tools mentioned, and no context about appropriate use cases or exclusions.

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