GetLocalDefinitions

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

No annotations are provided, so the description carries full burden. It only states the basic action and version support, with no mention of side effects, security requirements, error handling, or return behavior.

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?

The description is two sentences (16 words) with no redundancy. The main action is front-loaded, and every sentence provides essential information.

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?

For a simple retrieval tool with a fully described schema, the description is adequate. It does not need to explain return values since there is no output schema, but it could be slightly enhanced by clarifying what the source code output is.

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?

The schema already provides full descriptions for both parameters (100% coverage). The description adds no additional meaning beyond what is in the schema, merely restating the version support.

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 it retrieves local definitions source code from a class, which is clear. The phrase 'definitions include' is slightly ambiguous but does not obscure the main purpose. It distinguishes from sibling tools that delete or update local definitions, but does not explicitly differentiate from other GetLocal tools like GetLocalMacros.

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?

The description mentions it supports reading active or inactive versions, which gives some usage context but does not specify when not to use this tool or provide alternatives. There is no guidance on prerequisites, such as the class needing to exist.

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