debug.parsers

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only says it lists parsers—no mention of whether it's read-only, requires a session, or has side effects. The lack of traits like 'read-only' or 'session-dependent' leaves significant ambiguity for an agent.

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, clear sentence—no filler or unnecessary words. It's appropriately sized for a simple listing tool, though it could benefit from adding a brief clarification after the sentence, but that's optional. No structural issues.

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?

The tool is simple (1 param, no output schema, no nested objects), but the description omits critical context like session dependency and return format. With no annotations or output schema, the description should cover these basics to be complete for an agent; it falls short.

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?

With 0% schema description coverage and only one parameter ('session_id'), the description fails to explain what session_id represents (e.g., a hex string from session.open). No additional meaning is added beyond the schema's type definition, leaving the parameter's format and purpose unclear.

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 states it lists 'debug info parsers valid for this view', providing a clear verb ('List') and resource ('debug info parsers'). However, it doesn't specify what 'this view' refers to—likely a session context from a sibling tool like session.open—and with siblings like 'debug.parse_and_apply', it's unclear if this lists available parsers for that action. The purpose is adequate but lacks precision to distinguish from related sibling tools.

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 is provided on when to use this tool versus alternatives like 'debug.parse_and_apply' or when a session must be active. The sibling set suggests many tools depend on session state, but the description omits this prerequisite, leaving the agent to infer usage context.

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