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

Beyond readOnlyHint=true and openWorldHint=false, the description discloses permissions behavior (guests get a permission error), default date window and timezone, and the caveat that persons only filters the activity section. That is meaningful behavioral context the annotations do not carry.

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?

Dense but organized into three movements: what is returned, which filters exist, and formats/permissions. The output enumeration is long, yet each item names a distinct returned field, so little is wasted; a lead sentence naming the return categories would improve front-loading.

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?

For a 9-parameter, zero-schema-coverage, no-output-schema analytics tool, the description covers returned shape, filter semantics, defaults, enum behavior, and permission failure mode. An agent has everything needed to call it correctly without guessing.

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 0%, so the description must compensate, and it largely does: date formats and defaults, IANA tz, groupBy enum values with the special behavior of 'parent', and the fact that persons filters only activity. Only projectId and the exact semantics of milestoneId/labelId/cycleId are left implicit.

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 precisely that it returns the figures of one project's Team tab over a date range, and enumerates the returned blocks (KPIs, forecast, per-day, per-person, groupBy breakdown, activity list). The 'UN proyecto' scoping implicitly distinguishes it from workspace_stats and account_overview.

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 explains scoping filters, defaults for from/to (last 7 days) and tz (Europe/Madrid), and the membership precondition with the guest error. It does not explicitly route the agent away from workspace_stats, but the context for use is otherwise clear.

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