get_asset_flow_analysis_plan

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

No annotations are present, so the description carries the full burden. It transparently discloses the return format ('markdown-formatted'), content ('prompts for LLM analysis'), and methodology ('AI-powered analysis with AWS documentation validation'), which is sufficient for a read-only plan-generation tool.

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 front-loaded with a clear topic sentence and uses structured Args/Returns sections for additional clarity. It is slightly redundant ('Get...' followed by 'This tool returns...') but remains concise and well-organized.

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 that there are no annotations and no schema parameters, the description adequately conveys purpose, output format, and analysis context. Since an output schema exists, detailed return-value explanation is unnecessary; the description is complete for a zero-parameter plan tool.

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 input schema has zero properties and schema description coverage is 100%, so no parameter explanation is needed. The mention of 'ctx' in Args is not reflected in the schema, but it does not affect user-facing parameter semantics.

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 'Get' and names the resource clearly: 'comprehensive asset flow analysis plan'. It states the plan is for analyzing asset flows for security concerns, which distinguishes it from sibling analysis-plan tools like get_trust_boundary_analysis_plan.

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 clearly indicates when to use this tool by specifying its purpose: 'for analyzing asset flows for security concerns'. It does not explicitly name alternatives or exclusions, but the asset-flow scope provides clear contextual guidance.

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