Quarterback

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

Mentions documents are for 'review and analysis' but omits critical behavioral details like auto_analyze default behavior, workflow triggers, or side effects.

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?

Brief and front-loaded, but undersized for 9-parameter complexity; single sentence fails to justify its existence given schema gaps.

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?

Incomplete given rich sibling ecosystem (analyze, discuss, adopt); misses opportunity to explain advisory workflow integration and document lifecycle.

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?

Adds zero parameter context despite 0% schema description coverage; critical parameters like workflow_name, source_type, and auto_analyze lack semantic explanation.

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 basic action (add advisory document) and purpose (review/analysis) but fails to distinguish from sibling analysis tools or define 'advisory document' concept.

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 guidance on when to use vs. siblings like analyze_advisory_document, or workflow sequence (add before analyze?).

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