zins_get_casb_app_report

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

The description confirms the read-only nature, which aligns with the readOnlyHint annotation, and adds the behavioral constraint that the window must be 7- or 14-day. No contradictions. It does not detail permissions or rate limits, but the annotation already covers the safety profile.

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?

Three concise sentences, front-loaded with the main purpose, followed by the key behavioral constraint and output structure. No unnecessary words, well-organized.

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 no output schema, the description explains the output structure (one row per app with aggregated total). It also defines the window constraint. However, it omits mention of the limit parameter for pagination and default behavior, and the query parameter is well-documented but the time parameters are not. Overall, fairly complete but could be improved.

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?

Only 17% of schema parameters have descriptions (only 'query' is described). The description mentions the window interval but does not explain the time parameters (start_time, end_time, start_days_ago, end_days_ago) or their relationship. The 'limit' parameter is not addressed. With low schema coverage, the description fails to adequately compensate.

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 the CASB SaaS-application usage report, with one row per application and aggregated totals, for the purpose of seeing which cloud apps are accessed. It is specific about the resource and action, and distinguishes from sibling tools that are about settings, policies, or other analytics.

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 indicates it's for read-only analytics and specifies the window constraint (7-14 day interval), but does not explicitly state when to use this tool versus siblings or when not to use it. No exclusions or alternatives are mentioned.

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