zins_get_shadow_it_summary

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

Annotations already set readOnlyHint=true. Description reinforces read-only behavior and adds value by describing the return structure (single object with breakdowns) and window constraints, going beyond annotations.

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 sentences with front-loaded purpose. No unnecessary words. Efficient and well-structured.

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?

Describes return object but lacks explanation of parameters given 0% schema coverage. No output schema, so description must fully describe output; it partially does. Missing prerequisites and error conditions.

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?

Schema description coverage is 0%. Description only mentions window must be 7- or 14-day historical interval, but does not explain the four parameters (end_time, start_time, end_days_ago, start_days_ago) or their defaults. Insufficient compensation for missing schema descriptions.

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?

Clearly states it retrieves the aggregate Shadow IT summary dashboard. Specifies it is read-only analytics and includes org-wide totals and breakdowns by category and risk index, distinguishing it from sibling tools like zins_get_shadow_it_apps.

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?

Provides clear context on when to use: to get the summary dashboard with a required 7- or 14-day historical interval. Does not explicitly exclude alternatives but the constraint is helpful.

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