Archive ai tracking topic

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known, but the description does not disclose what archiving destroys, whether it is reversible, or what it does to related prompts/runs. 'Preserve immutable revisions' hints at retention but is not tied to the archive action, and the budget/retry-key sentence reads as unrelated boilerplate.

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?

Three short sentences, but they are not front-loaded with the actual operation and none of them explain archiving. The content is brief yet mostly filler, so it fails the 'every sentence earns its place' test despite its size.

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, non-open-world mutation with no output schema, the description should at minimum say what gets archived and what happens to dependent entities. Instead it omits the core action entirely, leaving the agent under-informed about a destructive call.

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 description coverage is 100%, with topic_id and project_id both documented (patterns and scope enforcement). The description adds no format, syntax, or scoping meaning beyond that, so the baseline 3 applies.

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 name says 'archive_ai_tracking_topic', but the description never mentions archiving or topics. It opens with the vague 'Manage project-scoped AI tracking' and spends its remaining sentences on 'immutable revisions, explicit budget consent, and stable retry keys', which do not describe what this tool does. A sibling-aware agent cannot distinguish it from create/update/list_ai_tracking_topic on the description alone.

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 when-to-use guidance is given relative to update_ai_tracking_topic or archive_ai_tracking_prompt. The only conditional clause, 'This does not start an automatic paid baseline', is a narrow exclusion about billing rather than a routing rule, so the agent still cannot tell when archiving is the right call.

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