verify_co_scientist_citations

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

No annotations are present, so the description carries the burden. It clearly frames the operation as one of checking citations against sources, but it does not disclose return format, failure behavior, side effects (e.g., network fetches or local file reads), or whether the operation is strictly read-only. This leaves moderate uncertainty in behavior.

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 well structured with a brief purpose statement followed by bullets and concise sections; the trigger list is slightly repetitive with the purpose but earns its place as usage guidance. No fluff.

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 simple two-parameter verification tool the description includes purpose, triggers, workflow position, and parameter semantics. However, there is no output behavior or return-value description, and no annotations, so the agent is left to guess what the tool returns after verifying citations.

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 0%, and the description compensates by explaining citations are a non-empty list and session_ids scopes artifact lookup. It adds the non-empty constraint and the semantic role of session_ids, which is beyond the bare property names, though it does not specify citation string format.

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?

States a specific action: verifying Co-Scientist citations against three concrete target types (URLs, artifacts, local files). The workflow-position references to start_hypothesis_verification and submit_verification distinguish it from those verification-workflow siblings, so an agent can tell it apart.

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?

Provides an AUTOMATIC TRIGGERS section enumerating exact conditions (preflight packet citations, verification report citations before submission, artifact/local-file references) and a WORKFLOW POSITION naming the precise stage between validation and verification/submission. This is explicit enough to route tool choice without needing to open sibling schemas.

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