Codebase Context

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes what information is retrieved but lacks details on how the tool behaves: it doesn't specify if this is a read-only operation, whether it requires authentication, potential rate limits, or what format the metadata is returned in. For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that clearly states the tool's purpose and scope. It's front-loaded with the main action ('Get codebase metadata') and follows with specific details, with no wasted words or redundant information. Every part of the sentence contributes meaning.

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 the tool's complexity (retrieving metadata with multiple aspects), lack of annotations, and no output schema, the description is minimally adequate. It lists what metadata is included but doesn't explain the return format, depth of information, or potential limitations. For a tool with no structured behavioral hints, more context would be helpful, but it meets a basic threshold.

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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides. A baseline score of 4 is appropriate for a zero-parameter tool, as there's no risk of undocumented inputs.

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's purpose as 'Get codebase metadata' with specific details about what metadata is included (framework information, dependencies, architecture patterns, project statistics). It uses a specific verb ('Get') and resource ('codebase metadata'), but doesn't explicitly distinguish it from sibling tools like 'get_component_usage' or 'get_team_patterns' which might provide overlapping or related information.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context for usage, or compare it to sibling tools such as 'search_codebase' or 'get_component_usage'. The agent must infer usage based solely on the tool name and description without explicit direction.

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