github_api_insights_get_time_stats_by_actor

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

No annotations are provided, so the description carries the full burden. It does not disclose any behavioral traits such as read-only, destructive, rate limits, or data scope. The description only states the action without any behavioral context, leaving the agent uninformed about side effects or access requirements.

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 a single sentence of 5 words, which is very concise. However, it is overly minimal and lacks essential details that would justify its brevity. Every word is earned, but the description would benefit from more content to be useful.

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, no output schema, and many sibling tools, the description is incomplete. It does not explain what time stats are, what actor_type refers to, or how the parameters relate. A more complete description would provide context for effective use.

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 has 100% coverage with parameter descriptions. The tool description adds no additional meaning beyond the schema. The baseline is 3 because the schema already documents parameters thoroughly, but the description does not enhance understanding.

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 states 'Get time stats by actor', which identifies the resource (time stats) and the grouping (by actor). However, it is vague because it does not explain what 'time stats' are or how they differ from other stats tools like 'get_time_stats' or 'get_summary_stats_by_actor'. The verb is clear but the purpose lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. There are sibling tools like 'get_time_stats_by_user' and 'get_summary_stats_by_actor', but the description does not mention any context, prerequisites, or exclusions. An agent would have no basis to choose this tool over others.

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