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

Beyond the readOnly/openWorld annotations, it discloses the per-type return contract (dataset rows with default 10/max 50, prompt template plus {{variables}}, context system prompt/knowledge/examples), the mandatory Source citation line, and the two failure modes (nonexistent code, private resource). That is unusually rich behavioral disclosure.

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 purpose and trigger, and each subsequent clause carries distinct information (formats, return shape, citation duty, failures). It is a dense run-on block rather than cleanly separated points, which slightly hurts scanability but no sentence is wasted.

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 full burden of describing return values and does so per resource type, plus error behavior and citation obligations. Nothing needed to call it correctly is missing.

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 baseline is 3, but the description adds real meaning: it documents the three accepted code formats (short code, 'author/name', 'code#v2' for pinned versions) and restates the rows default/max. The version-pinning format in particular is not in the schema.

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+resource ('Read one ContexteTech resource') and immediately distinguishes itself from sibling search_resources by describing the post-search retrieval role. An agent can separate it from search, fetch, and fill_prompt without opening any 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?

Gives explicit triggering conditions ('usually right after search_resources or when the user gives a code or page URL') and routes onward to fill_prompt for prompts. The alternative-tool relationship is named rather than left to inference.

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