agloop_get_plan

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

Describes a read operation with no side effects, which is adequate. However, it does not mention error handling (e.g., if plan doesn't exist) or any required permissions. With no annotations, the description carries the full burden and is minimally sufficient.

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?

Extremely concise – two short sentences with no unnecessary words. Every sentence adds value.

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 the tool's simplicity (0 params, output schema exists), the description covers the essential behavior. It could briefly mention that the plan is stored in plan.yaml/plan.md, but it's already implied. Overall, complete enough for its complexity.

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?

No parameters exist, so schema coverage is 100%. The description adds context about the return format ('raw file contents') beyond the empty schema, which is helpful. Baseline for 0 params is 4.

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?

Clearly states it reads the current plan (plan.yaml or plan.md) and returns raw file contents. Specific verb-resource pair distinguishes it from other 'get' siblings like get_logs or get_state.

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 on when to use this tool versus alternatives. With many sibling tools, an explicit context or exclusion would help the agent decide, but none is provided.

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