log_ppp

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

With no annotations provided, the description is the only source of behavioral disclosure. 'read-only' is a real behavioral guarantee that this tool will not change state, which is valuable. However, it says nothing about output format, whether it tails or returns a snapshot, or behavior when no PPP/MP session exists, so the behavioral disclosure is still incomplete.

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 short and contains no filler or unnecessary detail. It communicates the resource and safety characteristic in one compact phrase. It could be slightly more useful with a verb, but it is appropriately front-loaded for a zero-parameter log tool.

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 zero-parameter, no-output-schema tool, the description only needs to establish what data the command is about. 'PPP/MP log' does that, but it does not indicate whether the result is a complete log dump, a limited tail, or how it is ordered. This leaves a few practical usage questions unanswered, especially since many sibling logging commands exist.

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 input schema contains zero parameters, so there are no parameter semantics for the description to explain. The empty schema combined with the 100% schema description coverage means an agent needs no additional parameter guidance to invoke the tool successfully.

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 identifies the resource as a 'PPP/MP log' and labels it 'read-only', so an agent can tell this is a log-viewing command and not a mutating action. It lacks an explicit action verb, but the tool name 'log_ppp' and the resource phrase together make the purpose reasonably clear. It also offers a specific PPP/MP focus that helps distinguish it from other log commands.

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?

There is no guidance about when to use this tool instead of sibling log tools such as log_tail, log_wan, or log_filter. The description does not mention exclusions, prerequisites, or an appropriate context for requesting the PPP/MP log.

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