set_semantic_index_budget

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a session-state mutation but does not mention side effects, repeat-call behavior, persistence, error conditions, or what happens when the feature is not enabled.

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, front-loaded sentence with no filler words. However, its brevity comes at the cost of substance, especially for the parameter.

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?

With no annotations, no parameter documentation, and a single untyped-in-practice integer parameter, the description is far from complete. The output schema exists but does not compensate for missing parameter and behavioral semantics.

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?

The schema has zero description coverage for the only parameter, max_indexed_chunks, and the description does not explain it at all. The meaning, range, units, or effect of this integer are left entirely to the agent to guess.

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 states a specific action ('Adjust this session's semantic-index chunk budget') and a precondition ('when explicitly enabled'). It is distinguishable from sibling tools that focus on captures and diagnostics, though 'chunk budget' is not elaborated.

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?

The only usage signal is the vague phrase 'when explicitly enabled'; there is no guidance on when to invoke this tool versus any alternative, no prerequisites, and no explanation of what 'enabled' means or how to determine it.

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