get_eureka

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

With no annotations, the description must fully disclose behavior. It only states 'Get' implying read-only, but does not mention side effects, authentication requirements, rate limits, or any behavior beyond the single parameter. The text 'Get a specific EUREKA breakthrough document' is minimal and lacks behavioral context.

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 extremely concise with two sentences. The first sentence front-loads the purpose, and the second adds parameter guidance. No wasted words, achieving high information density.

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 the existence of an output schema (signal shows true), the description is nearly complete for a simple one-parameter get tool. However, it could mention that the name is a unique identifier or that the document includes breakthrough details, but the current version is adequate.

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 description adds meaning to the 'name' parameter beyond the schema by providing a clearer label ('EUREKA name') and concrete examples ('EUREKA_CACHE_SEMANTICA', 'ATOM_001'). This compensates for the 0% schema description 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 action 'Get' and the resource 'specific EUREKA breakthrough document'. The tool name 'get_eureka' is accurately described, and it distinguishes itself from siblings like 'get_protocol', 'get_skill', etc., by specifying a unique document type.

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?

No guidance on when to use this tool versus its siblings. The description does not mention prerequisites, context, or exclusion criteria. An agent would have no information about when to prefer get_eureka over other get tools.

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