bdesign_editor_get

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

Annotations declare readOnlyHint=true, and the description's 'Read' is consistent with that. It adds the context that the tool returns the timeline and revision, but discloses no other behavioral traits such as project selection behavior or response shape.

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 front-loaded sentence with no filler. It is concise, though it omits some contextual details.

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 tool with one simple parameter and a readOnly annotation, the description is minimally sufficient, but it lacks any mention of projectId or relationship to sibling read tools. An agent might know what it does but not precisely when to invoke it over alternatives.

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 0%, and the description never mentions projectId. The parameter name is self-explanatory, but the description does not compensate for the schema's lack of documentation or clarify the optionality implied by zero required parameters.

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' and names a concrete resource: 'current Editor timeline and revision.' It is clear what the tool does, though it does not explicitly differentiate itself from sibling tools like bdesign_editor_view or bdesign_editor_history.

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 given for when to use this tool instead of siblings such as bdesign_editor_history or bdesign_editor_view. The word 'current' implies a contrast with history, but no explicit when/when-not or alternatives are provided.

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