analyze_evidence_profile

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

With no annotations, the description must carry the burden of behavioral disclosure. It does disclose an automatic inspection of public repositories, which is useful. However, it does not mention whether the operation is read-only, requires authentication, has rate limits, or what side effects (e.g., network requests) may occur.

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 action and outcome. The second sentence provides a critical conditional behavior without excess. Every word earns its place, and it is well-structured for scanning.

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 description explains the core dual-mode behavior but omits details about the generated roadmap structure, how to handle cases where both repo and profileRef are provided, and potential limitations (e.g., private repositories). Given the complexity of five parameters and nested options, the description is functional but not fully complete.

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?

The schema covers 80% of parameters, so the baseline is 3. The description adds semantic value beyond the schema by clarifying that the 'repo' parameter can also accept a GitHub profile URL and that the tool will automatically inspect public repositories in that case, which is not evident from the schema's parameter description alone.

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 tool analyzes a GitHub repository or user profile URL and generates a learning roadmap, using a specific verb and resource. It distinguishes itself by mentioning both repo and profile modes, though it does not explicitly differentiate from sibling tools like get_roadmap_signal.

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 implies when to use the tool (for repo or profile analysis) and mentions an automatic behavior for profile URLs, but it does not explicitly state when to prefer this over sibling tools like compare_profile_and_repository_skills or generate_evidence_cards. No exclusions or alternative tool names are provided.

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