audit_local_sources

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

With no annotations, description must bear full behavioral disclosure. It describes outputs but does not clarify if the tool modifies sources, error behavior, or performance characteristics. Lacks detail on side effects or safety profile.

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-sentence description is concise and front-loaded with purpose and key outputs. No unnecessary words; every sentence adds value.

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?

Description covers basic purpose and outputs but lacks detail on report content, cross-ref graph specifics, and dead code detection scope. Given no output schema and simple parameters, more completeness would be beneficial.

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 100% and parameter descriptions are present. Description does not add meaning beyond the schema; it provides context that source_root is a download output dir, but that's already in the schema. Baseline 3 is appropriate.

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?

Description states specific verb 'Analyze' and resource 'downloaded sources', and lists deliverables: cross-ref graph, dead code, HTML report. It distinguishes from siblings by noting 'locally (no API)', making purpose clear.

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?

Description mentions 'locally (no API)', implying use after downloading, but does not specify when to use this tool versus siblings like query_local_graph or extract_table_dependencies. No explicit guidance on prerequisites or alternatives.

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