cyberqp_get_tenant_company_data

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

With no annotations, the description carries the behavioral burden itself. 'Get' clearly signals a read-only operation, and 'authenticated tenant's own' discloses that the operation is scoped by the caller's authentication context. For a simple zero-parameter read, this is adequate and unlikely to mislead.

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 brief parenthetical of the returned fields. Every word earns its place; there is no repetition or filler.

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, zero-parameter getter with no annotations and no output schema, the description is complete: it states the resource, the scoping identity, and the returned fields. An agent has 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?

The tool has zero parameters, so the schema provides no semantic content and the baseline is 4. The description adds value by listing the profile fields that the call returns, even though it does not need to explain any parameter behavior.

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 starts with a specific verb ('Get') and names a clearly bounded resource: the authenticated tenant's own company profile. Listing the fields (name, address, timezone, contact phone) removes ambiguity, and 'own' distinguishes this tool from sibling customer/account/event 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 phrase 'authenticated tenant's own' gives a clear scope, implying this is the tool for the current tenant's profile rather than customer or account data. It does not explicitly name alternatives or exclusions, so it stops short of a 5.

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