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

Annotations indicate not readOnly, not destructive, not openWorld. The description adds minimal behavioral context; it lists actions but does not disclose side effects, authorization needs, or limitations. Some sub-actions (e.g., archive_stale) may be destructive, conflicting with destructiveHint=false, but the description itself does not contradict annotations.

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 lengthy but organized as a list with sub-actions. The front-loaded summary is vague; the structure is functional but could be more concise and clearer for AI parsing.

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?

The tool has many sub-actions, and the description covers most but not all parameter details. Missing information like default values, enum choices, and action-specific behavior under different params. An output schema exists but does not compensate for incomplete action descriptions.

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. It lists actions and some parameters (e.g., detail_level, tier, commitment_id), adding meaning beyond the schema. However, it is not exhaustive and lacks structure for an AI to infer all valid parameter options.

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 lists many sub-actions but lacks a clear, specific verb+resource statement of what the tool does overall. 'Satellite view, commitments, loops, patterns & metrics' is vague and does not distinguish it from sibling tools.

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 explicit guidance on when to use this tool versus alternatives. The description merely enumerates sub-actions without explaining context or providing exclusions.

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