Archive ai tracking schedule

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates/destroys state. The description does not say what archiving does to the schedule, whether it is reversible, or what permissions are required; the vague 'Preserve immutable revisions, explicit budget consent, and stable retry keys' is not actionable and could even read as reassuring in a way that muddies the destructive framing. Only the 'no automatic paid baseline' line adds concrete behavioral value.

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?

At three sentences it is not bloated, but the middle sentence ('Preserve immutable revisions, explicit budget consent, and stable retry keys') is opaque boilerplate that earns no place, and the vague opener is front-loaded where the action verb should be. Under-specification disguised as conciseness.

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 destructive mutation with no output schema, the description should at minimum explain what archiving means (soft vs. hard, reversibility, effect on associated runs/prompts). None of that is present, leaving the agent with the vague 'Manage...' framing plus annotations to infer the rest.

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?

Both parameters (project_id, schedule_id) are fully documented in the schema with patterns and scope notes (100% coverage), so the schema carries the burden. The description adds nothing about parameter meaning, which is acceptable but no better than the baseline.

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 opens with 'Manage project-scoped AI tracking,' a vague verb+domain that never states what the tool actually does to a schedule. Only the title and tool name ('archive_ai_tracking_schedule') convey the archiving action; the description itself is closer to marketing framing than a statement of function, and it does not distinguish itself from update_ai_tracking_schedule or archive_ai_tracking_prompt.

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 when-to-use guidance, no mention of siblings like update_ai_tracking_schedule (the non-archiving alternative), and no prerequisites. The only routing-adjacent sentence is the negative disclaimer 'This does not start an automatic paid baseline,' which hints at a side effect rather than when this tool should be chosen.

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