fusion_list_threads

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

Annotations already cover readOnlyHint and destructiveHint, so the description's 'without modifying it' adds little beyond that. It does add the scope of 'active or named component', which is useful context, but it does not describe return format, pagination, or any thread-specific details. The description is adequate but not rich.

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 a single, well-structured sentence that front-loads the action ('Inspect thread features') and adds scope efficiently. Every word earns its place with 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 simple read-only list tool with one optional parameter and annotations covering safety, the description is largely complete. It specifies the scope and the read-only nature, and the lack of an output schema is mitigated by the fact that the operation is inspection. However, it does not describe the structure of the returned thread data, which is a minor gap.

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 0%, so the parameter 'component' has no schema description. The description clarifies that 'component' can refer to the active or a named component, giving meaning beyond the raw schema (string or null). However, it doesn't specify the expected format (name, ID, path) or behavior when null, leaving some ambiguity.

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 verb-resource pair: 'Inspect thread features' and adds the scope 'in the active or named component'. This distinguishes it from general feature lists like fusion_list_features and from thread creation (fusion_thread). It doesn't name a specific sibling, but the purpose is unambiguous and not a tautology.

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 explicit guidance on when to use this tool versus alternatives is provided. It implies read-only inspection via 'without modifying it', but does not mention when to use fusion_thread for thread creation or fusion_list_features for a broader feature list. The agent must infer usage from the name and limited description.

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