find_by_code

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

The description mentions return behavior (data or 'not found' message) but lacks explicit safety disclosure. With no annotations, the description carries full burden; it does not state whether the operation is read-only or has any side effects.

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?

Two concise sentences, front-loaded with the action. No wasted words. Efficiently communicates purpose and basic behavior.

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 two-parameter lookup tool with no output schema and no annotations, the description adequately covers purpose and return behavior. It could mention safety (read-only) but the information is sufficient for agent use given low complexity.

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 descriptions already cover both parameters (full_name, code) with examples. The tool description adds no additional meaning beyond what the schema provides. Baseline 3 given 100% schema coverage.

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 clearly states the tool's purpose: 'Найти объект по коду' (Find object by code). It distinguishes from siblings like 'find_by_name' by specifying the lookup key (code vs name).

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 implies usage when you have the code of an object, but provides no explicit guidance on when to use this tool versus alternatives like 'find_by_name' or when not to use it. No context about prerequisites or limitations.

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