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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context beyond them: case-insensitive punctuation-ignoring matching, exact-then-substring precedence, the GitHub fallback with an explanatory note, and the exact error payload shape.

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?

Front-loaded with the payload description, then matching rules, then fallbacks, then the routing hint. Dense but every clause carries information; the parenthetical link list and example are slightly verbose but not wasteful.

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?

With no output schema, the description carries the return-value burden and does so thoroughly (fields returned, GitHub enrichment, error shape), and it covers the single parameter's matching behavior completely.

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% so the baseline is 3, but the description adds genuine meaning: matching is case-insensitive, punctuation is ignored, and partial names work ('workforce' finds the Enterprise Workforce Training Platform), which the schema only hints at via examples.

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?

States a specific verb and resource ('Full details of one of Shlok's projects') and enumerates the returned content (results, metrics, tech stack, rank, GitHub details, links), which clearly separates it from list_projects and the other get_* siblings.

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?

Explicitly routes the agent: 'Use list_projects first when you don't know the name,' and describes the fallback chain (featured projects → public GitHub repos → error with all project names) so the agent knows what happens on a miss and how to retry.

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