Get Repository Context

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint flags. The description adds valuable behavioral context: it notes that missing files degrade gracefully, and it describes the output format (Markdown summary plus structured content). This extra context enhances transparency beyond annotations, earning a 5.

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 well-structured with a clear overview, usage directive, and a bulleted list of parameters. It is front-loaded with the main purpose, and every sentence adds value. Although it repeats some schema defaults, the repetition is minimal and serves to reinforce key information. The length is appropriate for a tool with 14 parameters.

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 (14 parameters, many optional) and the richness of available structured data (annotations, full schema), the description covers all necessary information: what it returns, graceful degradation, and the role of each parameter. It also references sibling tools for deeper dives. This is a complete and self-contained description, earning a 5.

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%, providing a baseline of 3. However, the description enriches each parameter with practical context, such as linking to sibling tools for more detail (e.g., includeWorkflows mentions 'use workflow_permissions_audit for that'), clarifying defaults, and explaining behavior. This goes well beyond the schema, justifying a score of 5.

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: 'Read baseline context for a GitHub repository' and enumerates all components. It distinguishes itself from siblings by recommending use at the start of SDLC workflows and explicitly referencing alternative tools for specific tasks (e.g., branch_protection_status for branch protection). This aligns with the high standard of a 5.

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 explicit when-to-use guidance: 'Use this tool at the start of any SDLC workflow to understand the codebase before planning or creating work items.' Additionally, parameter descriptions advise when not to use certain features (e.g., 'workflow_permissions_audit for permission details'), offering clear alternatives. This fully meets the criteria for a 5.

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