Set threads

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, which is a lower bar. The description does add real behavioral context beyond that: invalid input silently falls back to 6 rather than erroring. But it omits whether the change persists across sessions, what it affects, and whether it is reversible.

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?

Front-loaded and physically short, but the Args block merely echoes the input schema while the Notes line does all the work. Structure is fine; some content does not earn 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 one-parameter mutation tool with annotations but no output schema, an agent still lacks the setting's scope, persistence, and acceptable input range. The one genuinely useful behavioral fact (silent fallback to 6) is present, so it is not wholly inadequate.

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?

With 0% schema description coverage, the description must carry the load and does not. 'threads (int): The number of threads' restates the name and type with no valid range, bounds, or meaning (e.g. whether 0 means auto-detect). The 'defaults 6' note is the only added semantic.

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?

States a specific verb and resource: 'Set the number of threads for parallel processing.' An agent knows it is a configuration setter, and no sibling tool covers the same ground. However, it never says which processing this governs (builds, validation, workspace scans), so the scope is left vague.

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 when-to-use guidance, no prerequisites, no mention of alternatives or whether the setting is global or per-operation. The reader must infer the entire usage context from the verb 'set'.

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