Get capacity

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety and determinism profile is fully covered by structured data. The description adds only that the result is a computed budget breakdown with explicit 'unaccounted for' accounting, plus the ambiguous 'Nothing is assumed' remark, which is too vague to count as real behavioral disclosure.

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?

Two tight sentences, front-loaded with the core concept (168-hour weekly budget) followed by the breakdown components. No wasted text, though the trailing 'Nothing is assumed' is an unclear fragment that slightly dilutes it.

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 burden of describing the return value, and it does enumerate the main components (overhead, committed hours per area, focus windows, unaccounted time). It is adequate for a parameterless read tool, with only the vague final sentence leaving residual ambiguity.

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 tool takes zero parameters, so there is nothing for the description to clarify; the baseline for a parameterless tool is 4. The description correctly implies no input is required.

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 a specific resource — a weekly 168-hour time budget — and enumerates what it contains (overhead, hours committed per area, focus windows, unaccounted time), which is more informative than the title alone. It does not, however, distinguish itself from close siblings like summarize_week, find_gaps, or get_planning_context, which an agent would need in order to choose correctly.

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?

There is no statement of when to call this versus alternatives such as summarize_week or find_gaps, and no prerequisites or context triggers are given. The closing phrase 'Nothing is assumed' is cryptic and does not function as usable guidance.

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