Get System Properties

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

With no annotations provided, the description must disclose behavior itself, but it only says 'Query', which implies a read-only operation. It does not mention return format, pagination behavior, authentication requirements, or any constraints beyond those in the schema, leaving the agent to guess about important runtime characteristics.

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, straight-to-the-point sentence with no redundant words. It earns its place by clearly stating the tool's purpose without fluff, matching the front-loaded style of high-performing examples.

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 is simple and benefits from an output schema and well-documented parameters, making the minimal description somewhat adequate. However, it lacks context about what system properties are or when they are typically queried, leaving a slight gap for the agent in understanding the broader use case.

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 describes both parameters (limit and query) with explicit descriptions, including examples and constraints, achieving 100% schema coverage. The description adds no additional parameter context, so it meets the baseline but does not enhance understanding 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 clearly states 'Query ServiceNow system properties', specifying the action and resource, which distinguishes it from sibling tools like get_record or get_ci. However, it does not explicitly contrast with alternatives or provide additional scope details, so it lacks the explicit differentiation seen in top-tier examples.

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 provides no guidance on when to use this tool versus alternatives such as get_record or list_records. It only states the basic action without mentioning exclusions, prerequisites, or typical use cases, leaving the agent to infer usage from the tool name.

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