index_custom_content

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

No annotations exist, and the description fails to disclose behavioral traits such as whether this creates or updates content, authorization requirements, side effects, or rate limits. The only behavioral clue is 'deprecated', which is incomplete for safe invocation.

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 sentence with no wasted words, but it is too brief. Important context (e.g., operation behavior, alternatives) is omitted. It's concise but lacks substance.

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 complex nested object with 7 required parameters and no output schema or annotations, the description is insufficient. It does not explain how to use the parameters, return values, or expected outcomes. The deprecation note alone does not make it complete.

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 input schema has comprehensive descriptions for all 7 properties (100% coverage), so the description adds no new parameter information. Baseline 3 is appropriate as the schema already defines semantics.

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 action 'index custom content' and the target 'AskX in Slite', with an explicit deprecation warning. It distinguishes from siblings like delete_custom_content and list_custom_content by indicating a different operation (index/update vs delete/list).

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. The deprecation note hints at not using it, but there's no recommendation for a replacement or context for when indexing is appropriate.

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