nst_get_profiles

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

With no annotations, the description carries the full burden of disclosing behavior. It does not mention that this is a read-only operation, any required permissions, or whether the list is static or dynamic. It also fails to describe any side effects or limitations, leaving the agent to infer safety from the name alone.

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 concise sentence that is front-loaded and free of fluff. It communicates the core purpose efficiently without wasting words, achieving excellent conciseness for a simple listing tool.

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?

The tool has four parameters for filtering and pagination, but the description does not mention these capabilities, nor does it describe what the return value looks like in the absence of an output schema. The description is too minimal to fully inform an agent about how to effectively use the tool in a real scenario.

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 full coverage for all 4 parameters, so the baseline is 3. The description adds no extra meaning beyond what the schema already provides, such as indicating that 'page' and 'pageSize' control pagination or that 's' filters results. The description is neutral and does not mislead, hence a 3.

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 'List available NSTBrowser profiles' clearly states the action (List) and the resource (NSTBrowser profiles). It distinguishes from siblings like 'create_session' and 'nst_get_browsers' by targeting profiles specifically, making its purpose unambiguous.

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 provided on when to use this tool versus alternatives, such as whether to use it before selecting a profile or how it relates to session management. The description gives no context for choosing this tool over siblings like 'nst_get_browsers' or 'list_sessions'.

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