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

With no annotations, the description carries the full burden. 'Get info' strongly implies a read-only, non-destructive operation, which is a useful implicit disclosure. However, it does not explicitly state side-effect safety, permission requirements, or return behavior. For a zero-parameter getter, this is minimally transparent but not fully explicit.

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 a single sentence, extremely concise and front-loaded. Every word adds value, and there is no redundant or vague filler. It is appropriately sized for the tool's simplicity.

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 tool's simplicity (zero parameters, no output schema, no annotations), the description covers the essential invocation context: it tells the agent what the tool does and that it requires no inputs. It lacks details about the return structure or when to use it, but for a basic platform info getter, it is sufficiently complete for selection and invocation.

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 tool has zero parameters, so the schema covers everything with 100% coverage. The description adds no parameter information, but none is needed. Baseline for zero parameters is 4, and there is no deficiency to penalize.

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 function: 'Get info about Loyal Spark protocol on Base L2' uses a specific verb ('Get') and a clear resource ('info about Loyal Spark protocol on Base L2'). It distinguishes from siblings like get_platform_stats and get_my_profile, though 'info' is broader than these more specific sibling names.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions or preferred contexts, nor does it reference any sibling tools such as get_platform_stats or get_program_analytics. This is a clear gap for a tool with many related siblings.

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