get_top_over_due_controls_detail

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

No annotations provided, so description carries full burden. The description indicates a read-only fetch operation and details the return structure, but does not disclose potential side effects, authentication needs, or limitations. Adequate for a simple fetch.

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 moderately concise but uses a mixture of prose and docstring format (Args/Returns). The opening line is duplicated. Could be streamlined while retaining key info.

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 output schema is provided, the description covers purpose, parameters, and return values. It explains the period format and count default. However, it does not explain how 'top' is determined or any ordering, which might be needed.

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?

Adds meaning beyond schema: explains period format ('Q1 2024') and count as page size with default. Schema has 0% description coverage, so this compensation is valuable. However, the description mixes parameter details with return format, causing slight confusion.

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 it fetches controls with top overdue, distinguishing it from siblings like 'get_top_non_compliant_controls_detail' and 'fetch_controls'. However, the term 'top' is not explicitly defined (e.g., sorted by score or duedate).

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?

No guidance on when to use this tool versus alternatives (e.g., fetch_controls, get_dashboard_common_controls_details). It only describes parameters and return values without context.

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