mcp-repo-graph

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

With no annotations provided, the description carries full burden for behavioral disclosure. It describes the architectural flow pattern but doesn't reveal what the tool actually does with this flow - whether it executes it, traces it, visualizes it, or analyzes it. No information about permissions needed, side effects, performance characteristics, or what 'rendered' means in practice. The description provides architectural context but insufficient behavioral 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 reasonably concise - a single sentence that packs architectural information. However, it's not optimally front-loaded; it leads with architectural pattern rather than the core action. The architectural detail (ENTRY -> SERVICE -> HANDLER -> DATA) is useful but could be better integrated with the purpose statement.

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 1 parameter with 0% schema coverage and no annotations, but with an output schema present, the description is moderately complete. The output schema reduces the need to describe return values, but the description still lacks crucial information about what the tool actually does (execution vs visualization vs analysis) and proper parameter guidance. For a tool with architectural complexity implied by the flow pattern, more completeness is needed.

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 description coverage is 0%, so the schema provides no parameter documentation. The description mentions 'feature' in the context ('End-to-end flow for a feature') but doesn't explain what constitutes a valid feature parameter, expected format, or examples. It adds minimal meaning beyond the parameter name but doesn't adequately compensate for the complete lack of schema documentation.

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 states it's an 'End-to-end flow for a feature' with a specific architectural pattern (ENTRY -> SERVICE -> HANDLER -> DATA), which provides some purpose beyond just the name. However, it's vague about what 'flow' actually does - it doesn't specify if it executes, visualizes, analyzes, or traces this flow. The description distinguishes from siblings by mentioning the architectural layers, but the core action remains unclear.

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?

No explicit guidance on when to use this tool versus alternatives. The description mentions it's for 'a feature' and shows the architectural layers, but doesn't specify use cases, prerequisites, or when to choose this over sibling tools like 'trace', 'graph_view', or 'impact'. The architectural pattern hint provides minimal context but no actionable selection criteria.

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