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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description adds the meaningful detail that the default output is a 'compact timeline summary' rather than raw data, but discloses nothing about auth requirements for agentToken, error behavior, or limits on the summary.

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?

Two short sentences with no waste; the purpose is stated first and the parameter guidance second. Tight and front-loaded, though the phrasing is terse enough to feel slightly compressed.

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 read-only summary tool with annotations covering safety and no output schema, the description conveys what is returned (revision + compact timeline summary) and how the flag changes it. The main gap is that the two credential/identity parameters are undocumented.

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%, so the description must carry parameter meaning. It explains includeProject well (only for complete raw data), but projectId and agentToken are left entirely to the schema types, so compensation is only partial.

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?

States a specific verb and resource: reads the current revision plus a compact timeline summary of a Studio project. The purpose is clear, but it never names a sibling (e.g. studio_export_json or studio_get_guide) to differentiate when this read is preferred, so it falls short of a 5.

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 gives conditional guidance for one parameter ('Set includeProject only when complete raw data is needed'), which is real when-to-use guidance. However, it says nothing about when to choose this tool over the many read-oriented siblings like studio_export_json or studio_get_guide, leaving tool selection to inference.

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