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

Goes well past the annotations: public-repositories-only scope, exclusion of scheduled and automated commits, a 30-minute cache, and a documented failure return of {"error", "github"}. The readOnly/idempotent/openWorld hints already cover safety, and the description adds the operational facts an agent actually needs to interpret stale or missing data.

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?

Front-loaded with what is returned, then scope limits, caching, and error behavior, then the sibling pointer — a sensible order with little waste. 'Takes no input' mildly restates the empty schema, and the error-shape notation is slightly malformed, but neither costs much.

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 carries the full burden of describing returns and does so field-by-field (repository, message, date, link) plus counts. Caching, error behavior, and exclusions round out everything an agent needs to call and interpret 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?

There are zero parameters and the description states 'Takes no input', which matches the empty schema. Nothing more is required, though it adds no meaning beyond confirming the schema's emptiness.

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 combination with concrete scope: commit counts for 7 and 30 days, repositories touched this week, and the 12 most recent commits with named fields. It also carves out what is excluded (automated/DailyDiff commits, non-public repos), so an agent can distinguish it from portfolio siblings like get_profile without opening a schema.

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?

Explicitly routes the agent to get_profile (rightNow) for monthly focus, which is real alternatives guidance, and states 'Takes no input' so invocation is unambiguous. It stops short of a full when-not-to-use statement (e.g., that this is not a search or historical archive tool), so it is strong rather than exhaustive.

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