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

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing a five-minute cached snapshot, the returned fields (source URL, fetch time), README language preservation, the SHA-guarded pagination contract, and an explicit prompt-injection warning to treat README text as untrusted data. That last item is genuinely operationally important and absent from structured fields.

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 what is returned, then routing, then pagination, then the safety note — a logical order with no filler. It is dense and slightly long, but nearly every sentence carries a distinct operational fact.

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 burden and does so: it enumerates returned fields, the cache window, README language handling, and the pagination continuation path. An agent has everything needed to call and consume the result correctly.

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 75%, and the description supplies the missing relational meaning: readme.next_offset should be passed as readme_offset and readme.sha as readme_sha to continue the same version, and max_chars is implied by 'if more text is needed'. It doesn't restate bounds/defaults, which the schema already covers.

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 (Read) and resource (one public GitHub project's metadata and README Markdown), and even names the content facets (code blocks, links) and language behavior. An agent can distinguish it from search_github_projects without opening either schema.

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 names where full_name comes from (search_github_ai_projects/search_github_projects or user-supplied owner/repo), lists the task conditions that justify a call (installation, configuration, deployment, feature verification, closer comparison), and states when not to call it (optional; don't fetch every search result) plus the no-prior-search case.

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