system_get_tenant_info

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

With no annotations, the description carries the full behavioral disclosure burden. It discloses a license requirement (a form of access context) and the endpoint, but does not explicitly state that this is a read-only operation with no side effects, nor describe response behavior. It provides some context beyond the bare purpose.

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 concise and front-loaded with the core action, but the opening 'Get Tenant Info' is redundant with the following sentence 'Get your tenant license information.' The structure with license and endpoint info is efficient, earning a high score despite minor redundancy.

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 operation, the description provides essential purpose and a key prerequisite, but omits details about the 'request_data' parameter and response format. Since there is no output schema, some return value explanation would improve completeness, yet the tool's simplicity keeps it minimally adequate.

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 schema has one parameter 'request_data' with 0% description coverage, and the description does not mention or explain it. Since schema coverage is low, the description should compensate, but it offers no guidance on what to pass in this parameter.

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 'Get your tenant license information' with a specific verb and resource, unambiguously identifying the tool's purpose. It distinguishes this tool from all sibling tools, none of which relate to tenant license info.

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 mentions a required license (Cortex XSIAM Premium/Enterprise/Enterprise Plus) as a precondition, but does not explicitly state when to use this tool or mention alternatives. Usage context is implied rather than clearly specified.

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