monthly_time_report_by_user

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

The annotations already declare this as a read-only, idempotent non-destructive operation, so the description's main behavioral additions are valuable: crediting time to the work-item author rather than assignee, and keying users by login to avoid display-name collisions. These nuances go beyond what annotations provide and materially affect how results are interpreted.

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: a concise opening statement, a short clarifying paragraph about grouping semantics, and a clearly formatted argument list. Every sentence adds useful information and there is no redundancy or filler.

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 read-only report tool with an output schema and five optional parameters, the description covers all necessary context: aggregation basis, calendar month, group key semantics, defaults, and input formats. The presence of an output schema means return values do not need extra explanation, so the description is effectively complete.

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 description coverage is 0%, so the description carries the full burden for parameter meaning. It compensates thoroughly with an Args section explaining each parameter: instance auto-detection, comma-separated projects, default year/month, and valid group_by values. This gives the agent everything needed to populate arguments correctly.

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 produces a monthly time report aggregated by the user who logged the time. It distinguishes itself by explicitly noting grouping is by work-item author, not issue assignee, which helps differentiate from other reporting tools. However, it does not name any sibling tool directly, so differentiation from similar reports like user_time_summary is only implicit.

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 provides clear context about what the report does and explains the grouping semantics, which helps the agent understand when this tool is appropriate. It does not explicitly state when not to use it or name alternatives, but the defaults and argument explanations imply typical usage. No direct exclusion or alternative comparison is offered.

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