get_logcat

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read. The description adds the behavior of filtering by a case-insensitive fragment, but does not disclose any other side effects or limitations beyond what annotations provide. No contradiction.

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, approximately 15 words, directly starting with the verb and including only essential information. No filler.

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 read-only tool with three parameters and no output schema, the description is sufficiently complete. It explains the core action and the optional filter, and the device_serial parameter is documented in the schema. It could mention the return format, but logcat output is conventionally text and not necessary.

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 description coverage is only 33% (only device_serial has a description). The description adds meaning by stating 'recent' for the lines parameter and 'case-insensitive' for contains, but it does not detail the lines count limits or default, which are in the schema. This partially compensates for the low 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 uses the specific verb 'read' with the resource 'logcat lines', and clarifies the optional filter for case-insensitive text. This clearly distinguishes it from all sibling tools, none of which deal with logcat.

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 the tool is used for reading logcat, but it does not explicitly state when to prefer it over alternatives or mention any exclusions. Since there is no sibling logcat tool, the context is clear but not explicitly guided.

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