input_get_sweepdict

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

The description discloses that the tool returns a dictionary of sweep types and required fields, and 'get' implies a non-mutating read. However, because no annotations are provided, the description carries the full behavioral burden and does not mention prerequisites, invalid input_path behavior, or error conditions.

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?

A single, direct sentence with no wasted words. The core action is front-loaded, and the description stays appropriately minimal for a simple getter.

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 getter with no output schema, the description conveys the primary function and return content. However, the required input_path is not explained, and there is no usage or fallback guidance, leaving the definition only minimally viable.

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 description must compensate for the undocumented input_path parameter. It does not mention input_path at all, leaving the agent to infer that it is a path to an input object from the parameter name alone.

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 uses a specific verb ('Get') and identifies a clear resource: the sweep type dictionary. It also states what the dictionary contains ('available sweep types and their required fields'), which distinguishes it from sibling dictionary tools like input_get_modedict.

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 is given on when to use this tool versus alternatives such as input_get_modedict or input_get_fields. The description only states what the tool does, not the conditions under which it is the right choice.

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