gc_convergence

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

No annotations are provided, so the description carries the full burden. The description discloses no behavioral traits whatsoever — no mutation safety, no side effects, no prerequisites, no idempotency, nothing. The phrase 'Strategic vector tracking' plus 31 action names gives no behavioral information.

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 compact (a single list of action names). However, this isn't genuine conciseness — it's under-specification masquerading as brevity. There's no editorial judgment about what merits explanation; the entire payload is a bare enumeration.

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?

This is a highly complex tool with 23 parameters, 31 action variants, and no output schema. The description provides virtually no context: no action semantics, no parameter-action mappings, no return value expectations. For a tool of this complexity, a minimal viable description would need far more than an action-name list.

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?

Although schema description coverage is 100%, the schema only describes parameters at the level of 'Vector name', 'Max results', 'Notes' — mostly one-word field labels. The description adds literally nothing about parameter semantics because it only lists action names without mapping any to parameters. With 23 parameters and 31 actions, the relationship between which action uses which parameters is completely unexplained.

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 is a list of 31 action names with no explanation of what the tool actually does. 'Strategic vector tracking — the Fosferon evaluation model' is vague jargon with no verb+resource clarity. It gives no sense of what operations are possible or what the tool's core purpose is beyond the opaque 'Fosferon evaluation model' phrase.

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 zero guidance on when to use this tool vs alternatives. The description lists 31 actions with no explanations, no context for selection, and no when-to-use or when-not-to-use guidance. It doesn't reference any sibling tools or clarify the domain boundaries.

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