sublime_get_rule

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

With no annotations provided, the description carries the burden of behavioral disclosure. It transparently states that the output includes full detection source, MITRE techniques, and metadata, which is valuable context. It does not mention error cases or access requirements, but 'get' clearly signals a read-only operation.

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 sentences with no wasted words. The core purpose and key output contents are front-loaded, and the usage guidance is appended in a natural 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?

For a simple one-parameter lookup tool with no annotations and no output schema, the description adequately conveys what the tool returns and when to use it. It stops short of covering error behavior or prerequisite details, but nothing critical is missing for an agent 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?

The input schema already documents the single 'id' parameter with a clear description and example, so schema coverage is 100%. The description merely reinforces that lookup is by ID, adding little beyond the schema, which matches the baseline for high 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 clearly states the tool retrieves a specific Sublime Security rule by ID, listing the key content areas (MQL source, MITRE techniques, metadata). It also distinguishes itself from the sibling sublime_search by framing itself as the follow-up inspection step rather than a search operation.

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 explicitly instructs to use this tool after sublime_search to inspect complete rule logic, which provides clear ordering context. It does not explicitly list alternative tools or exclusions, but the single-parameter design and 'get specific rule by ID' framing make the intended use unambiguous.

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