get_daily_manager_briefing

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

With no annotations, the description carries the full burden, and it does disclose what it aggregates (portfolio health, overnight status transitions, expiring contractor insurance) and what it emits (health score, key changes, bottlenecks, task matrix). It does not state whether the call is read-only, how expensive/latent such a synthesis is, or any caching behavior.

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?

Purpose is front-loaded and the example utterances earn their space by making intent matching easy. There is mild redundancy between the synthesis sentence and the Returns block, which both restate portfolio health, bottlenecks, and the task list.

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?

With an output schema present and zero parameters, the description need not explain return structure in detail, and it still summarizes the report contents adequately. Purpose, trigger contexts, and synthesis scope are all covered, so an agent has everything it needs to invoke this 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 takes zero parameters, so there is nothing to document and the schema cannot be the source of ambiguity. Baseline 4 applies; the description adds no parameter guidance because none is required.

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 opens with a specific verb+resource ("Generate the daily executive briefing and prioritized action plan for permit managers") and then enumerates the exact inputs it synthesizes. It is clearly distinguishable from every sibling, which cover intake, fee estimation, requirement search, readiness checks, AHJ packets, and contractor verification.

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?

It gives concrete trigger contexts ("during morning standups or management planning sessions") plus three example user utterances, which is strong routing guidance. It stops short of the top score because it never states when NOT to use it or names an alternative sibling to prefer in adjacent situations.

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