Get Message Log

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

Annotations already declare readOnlyHint=true. The description adds that results are filtered by level/tag and returned newest first, providing useful behavioral context beyond read-only status.

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 one sentence plus a short clarifying phrase. It front-loads the purpose and includes essential details without extraneous words.

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, the description need not explain return structure. It adequately covers filtering and sorting for a simple retrieval tool, though it could mention the 'limit' parameter.

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 explains 'level' (with possible values) and 'tag' (with example), but does not mention the 'limit' parameter. Schema coverage is 0%, so the description partially compensates but misses one parameter.

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 'Get QGIS message log entries' with filtering options, distinguishing it from unrelated sibling tools like 'get_layers' or 'execute_processing'. The verb 'Get' and resource 'message log' are specific.

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 lists filter parameters and sorting order, but does not explicitly state when to use this tool versus alternatives. However, no other sibling tool retrieves logs, so usage is implicitly clear.

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