veto_discover

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

Description claims it stores results in Veto memory (side effect), contradicting the readOnlyHint annotation which implies no state changes. This is a serious inconsistency. No mention of authorization needs or other behavioral traits.

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?

Two sentences, front-loaded with the primary purpose, no unnecessary words. Efficient and clear.

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?

Despite explaining scan contents and usage timing, the contradiction with annotations leaves a major gap. No explanation of safety, idempotency, or that the tool is read-only (contradicted). Incomplete for a mutation-like tool.

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 covers all three parameters with 100% coverage. Description adds minimal value beyond the enum names for depth and the default for store. Adequate but not enhanced.

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?

Clearly states scanning a project directory and building a context map with specific components. Distinguishes from siblings like veto_project_map_get by noting it stores in Veto memory and is for initial or after-major-changes use.

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?

Explicitly states 'Call this once per project or after major structural changes.' Provides clear usage context but lacks explicit when-not-to-use or alternatives.

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