get_code

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

Annotations already mark readOnly and idempotent. Description adds 'Always reads from disk — always current, never stale', which confirms freshness behavior without contradicting annotations.

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?

Three concise sentences. Every sentence adds value: purpose, freshness guarantee, prerequisite call, optional usage, language limitation. No fluff.

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 full schema coverage, comprehensive annotations, and no output schema, the description covers all key aspects: what it does, when to use it, how to use parameters, limitations, and a tip for sibling tool usage.

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 100%. The description adds non-obvious semantics: omitting symbol yields module-level constants and assignments, and the tool is Python-only. These clarifications go beyond the schema property descriptions.

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?

Clearly states the verb 'Get' and resource 'full source of a single function or class by name'. Differentiates from sibling tools like get_signature (discovers symbols) and implies read_file for other languages.

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 advises to call get_signature first to discover symbol names and line ranges. Specifies when to omit symbol (module-level constants) and that Python files only, with alternative for other languages (read file directly).

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