Browse the canon

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and locality are covered; 'Works offline' merely restates openWorldHint=false. The description adds no information about what a browse call returns (a list of child nodes? text snippets?) or whether results are paginated, which matters for a browsing tool.

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?

A single front-loaded sentence with no filler; the canonical resource is named first and the accepted values follow. The dense parenthetical example list is efficient, though the specific identifiers would read better separated from the prose than embedded mid-sentence.

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 three parameters, no output schema and no parameter descriptions, the definition leaves two meaningful gaps: the return shape of a browse call and the meaning of limit/offset. Offline availability is the only behavioral fact supplied, so the definition is adequate but not complete for an agent that needs to page through results.

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 description must carry the parameter burden. It does valuable work for 'node' by listing legal identifier forms, but 'limit' and 'offset' are never mentioned, leaving pagination semantics to be guessed from defaults and min/max alone. Partial compensation only.

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 a specific verb (Browse) and resource (the Tipiṭaka canon) and enumerates the accepted node kinds: canon, sutta, vinaya, abhidhamma, collections (dn, mn, sn, an, dhp...) and sections (sn56, an4, kv1). That is far more concrete than the title alone. It does not, however, distinguish this from siblings like search_texts or get_text, so an agent must infer the difference.

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?

Usage is implied rather than stated: the hierarchical node examples suggest this is the tool for walking the canon structure before fetching texts. There is no explicit when-to-use/when-not language and no mention of the obvious alternative (search_texts) or of how browsing relates to get_text or resolve_reference.

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