select_spread

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Select a spread' without any information on side effects, required state, or what the tool actually does (e.g., changes active spread, focuses UI). This is insufficient.

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 extremely short (3 words), which is under-specification rather than effective conciseness. It lacks essential details to be useful.

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 the tool has two parameters (one with an enum), no output schema, and no annotations, the description is incomplete. It does not explain what selecting a spread entails, what happens upon success, or how to interpret results. Sibling tools typically have more informative descriptions.

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 50% (only spreadIndex has a description). The tool description adds no additional meaning to the parameters; 'Select a spread' does not clarify the role of selectionMode or the format of spreadIndex. The description does not compensate for the schema gaps.

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 'Select a spread', which is a verb+resource pair. However, it is vague because 'select' is ambiguous—it could mean making a spread active or just choosing it for some operation. Among sibling tools like get_spread_info or set_spread_properties, the distinct purpose is unclear.

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 such as navigate_to_page or get_spread_info. The description does not mention prerequisites, context, or exclusions.

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