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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the access prerequisite ('Requires strategy management rights') and the list of what the guide contains, which tells the agent this is a static reference document rather than live strategy data.

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?

Three short sentences, front-loaded with what is returned, followed by usage context and the permission prerequisite. No filler or restatement of the title.

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?

With a 0-parameter schema and an output schema present, the description need not explain return structure, and it usefully summarizes the guide's contents and the auth requirement. The only gap is the absence of explicit routing guidance relative to get_strategy and get_innovation_template.

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 tool takes zero parameters, so there is no parameter semantics to document; baseline 4 applies. The description correctly does not waste space on inputs and instead describes the returned content.

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?

Clear specific verb and resource: returns a 'shared conversational capture guide' including readiness criteria, creation schema, and an example. An agent knows exactly what artifact it retrieves. It does not, however, differentiate itself from the sibling get_innovation_template, which appears to play the same role for a different resource.

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?

'Supports interactive capture and drafting from existing material' implies the usage context (preparation before create_strategy), but the description never states explicitly when to call this versus get_strategy or get_innovation_template, nor when it is unnecessary. Usage is inferable rather than directed.

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