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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the compact-versus-full behavioral distinction, which is useful, but it does not disclose error behavior, authentication requirements, or what 'authorization context' contains. No contradiction with annotations exists.

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, front-loaded sentence states the core purpose and optional variation with no wasted words. Every clause earns its place.

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?

This is a simple one-optional-parameter, read-only tool with an output schema, annotations, and full parameter documentation. The description, combined with the schema and annotations, gives an agent everything needed to invoke it correctly.

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 100%: the detailLevel parameter is fully described with an enum and default. The description merely echoes the compact/full distinction without adding new semantic information, so it meets the baseline but does not exceed it.

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 ('Return') and identifies a clear resource: the current user's identity and authorization context. It also signals an optional mode ('compact' vs 'explicit full profile detail'), which distinguishes it from the device-, server-, and organization-focused sibling tools.

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 description clearly establishes when to use this tool: when the current user's identity or authorization context is needed. It also implies the compact/full choice through the detailLevel parameter. However, it does not explicitly contrast it with related sibling tools like validate_session or get_organization_context, so it stops short of full routing guidance.

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

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds that context is 'selected' rather than exhaustive, but does not disclose pagination behavior, open-world response characteristics, or that 'details' is always included; these are left to the schema. No contradiction with annotations.

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 sentence with no filler, front-loading the action and resource before the optional context list. Every element earns its place, and the structure is immediately scannable.

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 a rich input schema, output schema, and read-only annotations, the minimal description is mostly adequate. However, for a context-aggregating tool with nested options and multiple siblings, a short usage pointer or completeness note would improve orientation; the current text omits 'details' and 'maintenanceWindows' from its enumeration.

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 100%; deviceId, include, and noteOptions are already described with enums, ranges, and defaults. The description's list of context types roughly mirrors the include enum but omits details and maintenanceWindows, so it adds little semantic value beyond the schema. Baseline 3 is appropriate.

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 ('Load'), names the resource ('a device'), and enumerates the context areas included (monitoring, asset, lifecycle, note, custom-property, task). This clearly differentiates it from sibling context loaders like get_organization_context and get_scheduled_task_context by naming the device resource.

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 description implies this tool is for retrieving a device with selected context, but it never states when to prefer it over search_devices or get_organization_context, nor does it give exclusions. Usage context is inferable from the name and resource type, but no explicit when-to-use guidance is provided.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral nuance by noting the tool returns 'bounded' results and that full/all components must be explicitly requested. This complements the annotations without contradicting them.

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 that states the purpose and key behavioral requirement ('Request full/all explicitly') without any wasted words. It is appropriately concise for a tool whose schema carries detailed parameter information.

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 tool with five parameters, nested objects, and an output schema, the description is terse but the schema fills in all parameter details. The description mentions the key components and the explicit request requirement, which is sufficient for an agent to understand the tool's scope. No critical information is missing given the schema and annotations.

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 100%, so all five parameters are documented in the schema itself. The description adds a high-level hint about requesting full/all, which relates to detailLevel and the 'all' flags, but it does not elaborate on individual parameter semantics beyond what the schema already provides.

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 clear purpose: 'Load compact organization details plus selected bounded children, limits, and custom-property context.' It identifies the resource (organization) and the specific components (children, limits, custom properties) that can be included, distinguishing it from sibling tools like get_device_context or get_scheduled_task_context.

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 description implies usage when organization context is needed and hints at how to request full details ('Request full/all explicitly'), but it does not explicitly state when to use this tool over alternatives like search_organizations or get_current_user. There is no when-not-to-use guidance or mention of alternative tools.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds value by clarifying the distinction between aggregate and per-device execution status, which is not fully captured in the schema. This enhances behavioral understanding beyond the structured fields.

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 that efficiently conveys the main purpose and the optional status feature without any waste. It is concise and well-structured.

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 an output schema present and a simple 3-parameter read-only tool, the description covers the essential behavior. It does not mention prerequisites like task existence, but these are implicit and the schema and annotations fill in the remaining gaps. The description is adequate for an agent to call it correctly.

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 100%, so the baseline is 3. The description adds meaning by explicitly naming 'aggregate or per-device' status, which maps to includeStatus and detailedStatus respectively, and clarifies the relationship between these booleans beyond the schema's individual descriptions.

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 verb ('Load') and resource ('scheduled-task definition') and clearly distinguishes the tool's scope from siblings like list_device_scheduled_tasks, which lists tasks rather than loading a specific one. It also mentions the optional status retrieval, making the 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?

The description implies usage when a specific scheduled task's definition or status is needed, but it does not explicitly contrast with sibling tools or state when not to use it. No alternatives or exclusions are mentioned, leaving the agent to infer from the name and context.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the optional includeTime behavior, which is useful. It doesn't mention response format or error cases, but the output schema likely covers return values.

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?

One concise sentence with no wasted words. The main purpose is front-loaded, and the optional parameter is mentioned naturally.

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 simple read-only status tool with one optional parameter and an output schema, the description is nearly complete. It could explicitly state that no authentication is required or that it's safe to call, but the annotations already convey that.

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 100%, so the schema already documents the includeTime parameter. The description mentions 'optionally including the server clock,' which aligns with the parameter but doesn't add new meaning beyond the schema.

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 verb ('Check') and resource ('N-central service health and API version'), and adds the optional server clock detail. This clearly distinguishes it from sibling tools like validate_session or get_current_user, which target different resources.

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 description implies this is a health/status check tool, and the readOnlyHint annotation reinforces that it is safe to call. It doesn't explicitly name alternatives or when-not-to-use, but the context is clear enough for an agent to select it for health/version checks.

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

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

Annotations already cover the read-only and non-destructive nature. The description adds meaningful behavioral context: bounded pagination, a compact default projection, and the service-org unsupported constraint, all of which are not inferable from annotations 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?

Two sentences, no filler. The core purpose and scope are front-loaded, and the detailLevel guidance is placed where it matters most. Every clause carries signal.

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 moderately complex 8-parameter tool with an output schema, the description conveys the essential non-obvious details: scope limitations, pagination bounds, default projection, and when to request full records. The output schema handles return-value specifics, so nothing critical is missing.

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 coverage is 100%, so the baseline is 3, but the description adds value by explaining the trade-off between compact and full detailLevel and stating the default behavior. This gives the agent actionable selection guidance beyond the schema's enum descriptions.

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 names a specific verb and resource: 'List current active monitoring issues'. It also narrows scope to customer or site and explicitly excludes service-org scope, which clearly distinguishes it from sibling tools like list_job_statuses or search_devices.

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?

It gives clear context: active issues for a customer/site, service-org unsupported, and provides a decision rule for detailLevel ('use full only when complete upstream records are required'). It does not name alternative tools for comparison, but the scope constraints effectively guide when to use this tool.

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

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description is consistent with those annotations but adds little behavioral context beyond the per-device scoping; no additional side effects, pagination, or session requirements are disclosed.

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 focused sentence that states the action, the object, and the scope with no wasted words. It is front-loaded and easy to parse, which is ideal for an agent selecting among many tools.

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 simple one-parameter read-only list operation, the description covers the essential usage context. The output schema is present, so return-value details do not need to be restated, and the annotations cover the read-only and non-destructive behavior. Nothing critical appears missing.

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 already provides 100% coverage for the single deviceId parameter, including a clear description. The description's mention of 'one N-central device' aligns with the parameter but does not add new semantic meaning beyond what the schema already documents, so the baseline score applies.

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 ('list') and resource ('scheduled tasks') scoped to 'one N-central device', making the tool's purpose immediately clear. The wording also distinguishes it from sibling tools like list_active_issues and list_job_statuses by naming the resource and scope directly.

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 description gives no guidance on when to use this tool versus alternatives such as get_scheduled_task_context or list_job_statuses. It implies per-device usage, but does not state prerequisites, exclusions, or conditions that would route an agent to this tool instead of a sibling.

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

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

Annotations already signal a safe read operation via readOnlyHint and destructiveHint. The description adds meaningful behavioral detail beyond annotations: 'local filtering' indicates filters are applied after retrieval, 'bounded pagination' tells the agent results are limited and pageable, and 'compact default projection' explains the default output shape without requiring the agent to inspect the schema first.

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, information-dense sentence with zero filler. The core action and resource are front-loaded, followed by three distinct behavioral characteristics that summarize the tool's personality. Every phrase earns its place.

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 an 8-parameter read-only listing tool with a complete output schema and fully described parameters, the description covers the essential behavioral context: what is listed, how results are filtered, how pagination works, and what the default projection is. It could name the required orgUnitId explicitly, but the schema already requires it, so the agent can proceed confidently.

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 100%, so the baseline is 3. The description adds value by clarifying that filters are local and pagination is bounded, which helps an agent reason about how parameters like since, status, deviceId, pageSize, and pageNumber interact. It also reinforces that the default detailLevel is compact, aligning with the schema's default description.

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 opens with a specific verb and resource: 'List asynchronous N-central job statuses.' It also distinguishes this tool from siblings by adding behavioral qualifiers—'local filtering, bounded pagination, and a compact default projection'—so an agent can differentiate it from list_device_scheduled_tasks and other list/search tools.

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 description implies the tool is for retrieving job statuses, and the resource scope is clear, but it does not explicitly state when to prefer this tool over alternatives or when not to use it. The sibling list does not include a directly competing 'list jobs' tool, so the lack of explicit exclusions is less harmful, but guidance is still only implied.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the constraint that only reviewed adapters are accepted, which is useful context, but does not disclose other behaviors like output format or error handling. It does not contradict annotations.

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, focused sentence that front-loads the core purpose and includes a key limitation. No wasted words, and the structure is efficient.

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?

Despite having an output schema and annotations, the tool has 10 parameters and two report types. The description gives no guidance on selecting reportType or understanding the tool's scope, leaving the agent to rely entirely on the schema. For this complexity, the description is too sparse to be fully self-sufficient.

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 100%, so all parameters are documented. The description does not add any parameter-specific meaning beyond the schema, which is acceptable given the baseline of 3 for full schema coverage.

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 the tool runs a reviewed read-only report adapter, which is a specific verb and resource. It distinguishes itself from siblings by focusing on reports, but does not fully define what a report adapter is. The constraint about arbitrary REST methods adds clarity.

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 explicit guidance on when to use this tool versus alternatives. It mentions that arbitrary REST methods or paths are not accepted, but does not suggest what to use instead. The description lacks context on prerequisites or situations where this tool is appropriate.

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

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

The annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds useful behavioral context by noting 'bounded filters and pagination' rather than an unbounded search. It does not discuss result limits, case-insensitivity, or authentication, though the output schema and parameter descriptions cover some of that. This is adequate but not exceptional.

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 sentence with no filler: the verb, scope, and search modes are front-loaded. 'global or organization-scoped' and 'bounded filters and pagination' pack meaningful constraints into a compact phrase, making the description easy to scan and act on.

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 tool with 11 optional parameters, a fully documented schema, a rich output schema, and safety annotations, the description provides enough high-level orientation for an agent to select and invoke it correctly. It could have been slightly more explicit about name-vs-pagination mutual exclusivity and the orgUnitId scoping, but those details are already captured in the parameter 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 100%, so the input schema already documents all 11 parameters with constraints, enums, and descriptions. The tool description's mention of 'human name or bounded filters and pagination' maps loosely to the name, select, and pagination parameters but adds no semantic detail beyond what the schema provides. Baseline 3 applies.

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 opens with a specific verb ('Search') and identifies the resource ('N-central device inventory'), then states scope ('global or organization-scoped') and the two main access modes ('human name or bounded filters and pagination'). This clearly separates it from sibling tools like search_organizations or get_device_context.

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 'global or organization-scoped N-central device inventory' phrasing gives an agent clear context for when to use this tool: when locating devices by name or filters. It does not explicitly name alternatives or state exclusions, but the target use case is evident without needing to open the schema.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is covered. The description adds useful behavioral context by noting bounded filtering/pagination and flagging that customer-scoped site listing is PREVIEW and may change. This goes beyond the annotations without contradicting them.

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 two concise sentences with no filler. It front-loads the core purpose immediately and adds the preview caveat as a necessary second sentence.

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 a rich output schema, full parameter documentation, and annotations covering safety, the description is largely sufficient. It covers entity types and search modes, and the preview caveat addresses a key stability concern. A small gap is the lack of explicit sibling-tool routing, but that is not essential given the schema richness.

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 100%, so the baseline applies. The description adds high-level context like 'human name' and 'bounded filtering and pagination,' but the individual parameter semantics are already fully documented in the schema.

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 tool finds service organizations, customers, sites, and organization units by human name or bounded filtering and pagination. This is a specific verb plus resource, though it does not explicitly differentiate itself from sibling tools like search_devices.

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 description implies usage contexts: name-based search versus bounded filtering/pagination, and warns that customer-scoped site listing is PREVIEW. However, it does not explicitly say when to prefer this tool over search_devices or other siblings, nor does it mention exclusions.

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

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, covering safety and side-effect profile. The description adds the behavioral trait that no token material is returned, which is a valuable security detail beyond annotations. It also implies a boolean/success response. No contradictions.

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 sentence that is front-loaded with the verb and resource, followed by a concise behavioral qualifier. There is zero wasted text, and the structure is ideal for quick agent comprehension.

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 no parameters, a simple purpose, and an output schema exists (so return values are structured elsewhere). The description covers the purpose and a key behavioral trait. Given the annotations, everything an agent needs to call and interpret this tool is present.

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 tool has zero parameters, so the input schema trivially covers everything. With no parameters, there is nothing for the description to explain. The description does not need to add parameter meaning; baseline for 0 params is 4.

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 ('Confirm') and a clear resource ('current authenticated N-central API session'), and adds the qualifier 'without returning token material', which precisely defines what the tool does and distinguishes it from any sibling that might return session or user data. It is unambiguous and actionable.

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 description clearly implies its use case (validating the current session) and the 'without returning token material' phrase helps differentiate it from tools like get_current_user. However, it does not explicitly name alternatives or state when NOT to use it, leaving some inference to the agent. This is a minor gap.

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