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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description spends its space well by disclosing the counting rules: archived/completed projects never count, demo projects only with demo=true, and the time zone resolution chain ending in UTC with timezone_fallback=true. That is meaningful behavior an agent could not infer from the schema alone.

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?

Effectively one dense, front-loaded sentence with the resource and the metric list up front, then the exclusion and time zone rules. Nesting parentheticals makes it slightly hard to scan, but nothing is wasted.

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 no output schema, the description usefully enumerates the returned metrics and the needs-list precedence order (retake, issue, review, overdue, due_today), which is exactly what an agent needs. It omits only minor context such as permissions beyond 'Read tier' or the shape of the needs list items.

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 coverage is 100%, so the baseline would be 3; the description goes further by explaining the zone fallback chain (zone → org time zone → UTC) and surfacing the timezone_fallback response flag, and by restating what demo=true actually includes. This adds semantics beyond the terse schema strings.

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?

States a specific verb+resource (returns the organization's Today summary, GET /today) and enumerates the exact metrics returned (due_today, closed_today, awaiting_check, retake, photos_verified_7d, needs list). This clearly distinguishes it from list/detail siblings like tascan_list_tasks or tascan_org_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 implies usage (a read-tier dashboard rollup) and clarifies counting semantics, but never states when to prefer this over tascan_org_analytics, tascan_project_digest, or tascan_list_issues, nor any prerequisites. Task-level guidance is left to inference.

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