assess_legacy_codebase

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

No annotations are provided, so the description carries the full burden. It lists what is analyzed and returned, but does not disclose side effects, permissions, performance implications, or non-destructive nature. For a read-like tool, more explicit behavioral context would help.

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 efficiently convey the purpose, analysis domains, and return values. No unnecessary words or repetition. Front-loaded with verb and resource.

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?

Given no output schema and one input parameter, the description covers purpose, input, and output fairly completely. Could mention prerequisites or output format details, but for a simple tool it is adequate.

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 single parameter project_dir is described as 'Absolute path to the project directory to assess', which aligns well with the tool's purpose. Schema description coverage is 100%, and the tool description adds context about it being a legacy codebase.

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 assesses legacy codebase for migration readiness, with specific analysis areas and returns. It distinguishes from sibling tools like forge_assess and analyze_component_library by focusing exclusively on legacy codebase migration assessment.

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 does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among sibling tools. Use is implied for assessing legacy codebase migration readiness, but no exclusions are given.

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