get_org_sleep_summary

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

With no annotations, the description must carry transparency. It explains date selection logic, parameter defaults, and return format, but does not declare safety (read-only), permissions, or behavior under errors. The inclusion of concurrency hints at internal behavior, but overall it leaves important aspects implicit.

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 well-structured with a one-line summary, a line explaining date selection logic, a bullet list of parameters, and a return format outline. It is front-loaded with key information and every sentence adds value, though it is somewhat lengthy due to the parameter list. Structure is clear and efficient.

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 the tool has 6 parameters and an output schema, the description covers the main functional aspects: date selection modes, parameters, and return structure. However, it omits information about pagination, ordering, or handling of missing data. The concurrency and max_users hints are present but not fully explained. Overall, it is reasonably complete for basic usage.

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 input schema lacks any descriptions (coverage 0%). The description compensates fully by listing all six parameters with formats, defaults, and the critical mutual exclusivity rule for date selection. It adds significant meaning beyond the schema, making it very helpful for the agent.

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 provides a bulk sleep summary across users in the org using the verb 'get' and resource 'org sleep summary'. It distinguishes from sibling tools like get_sleep (individual) and get_org_scores_summary (scores) by explicitly labeling it as 'Bulk' and specifying the domain (sleep).

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 does not explicitly compare to alternatives or provide guidance on when not to use. It implies usage for org-level sleep summaries via 'Bulk' but lacks explicit exclusion criteria or mentions of sibling tools. This is borderline implied usage, falling short of clear guidelines.

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