convergeqa_critique_packet

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

With no annotations provided, the description must disclose behavioral traits. It mentions fetching and optional file writing, but does not clarify whether it modifies server state, requires authentication details (though parameters exist), or what happens on file write conflicts. It also does not discuss rate limits, data size, or error conditions.

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 a single sentence, which is concise but overly brief. It lacks structured information and does not front-load critical details like required parameters (session_id) or authentication prerequisites. Being too short can lead to ambiguity.

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 7 parameters, no output schema, and multiple sibling tools, yet the description does not explain what a 'Critique packet' is, how the output is used, or how to configure authentication. It fails to provide adequate context for an agent to use it correctly without additional knowledge.

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 only 43%, meaning many parameters (session_id, output, credential_kind, redact_private_urls) lack descriptions. The description does not explain these parameters beyond the basic fetch/write action. For example, session_id is not described at all, and credential_kind options are not explained. The description adds minimal semantic value.

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 clearly states the verb 'fetch', the resource 'Critique packet JSON', and an optional side effect of writing to a path. This distinguishes it from sibling tools like convergeqa_critique_export (likely exports in another format) and convergeqa_critique_start (starts a session). The mention of 'owner-authenticated' adds specificity.

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?

The description provides no guidance on when to use this tool versus the many sibling tools. It does not include when-not-to-use or alternative suggestions. An agent would have no context to differentiate between convergeqa_critique_packet, convergeqa_critique_export, or convergeqa_iterate_packet.

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