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

The description discloses important side effects beyond the annotations: a staged story is marked consumed, an assigned story remains the top until status changes, and the tool returns an empty-inbox message when neither exists. It also explains identity/project resolution from the agent key and the return shape, all consistent with readOnlyHint=false and idempotentHint=false.

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 dense but front-loaded: it starts with the core action and then layers selection logic, side effects, return shape, and usage trigger without redundant sentences. Every sentence contributes to correct invocation.

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 no output schema, the description explains the returned story context, the source field, and the empty-inbox case. For a no-parameter tool with fallback selection and a consumption side effect, an agent has everything needed to call and interpret it correctly.

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?

There are zero parameters, so the baseline is 4, and the description appropriately states that the tool takes no arguments and resolves projects and identity from the agent key. That adds useful context beyond the empty schema without needing parameter-level 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 states a specific verb and resource: pulling the next story to implement, with explicit staged-vs-assigned selection logic. It clearly distinguishes this tool from siblings like get_story, list_stories, and get_story_context by describing its unique selection and return behavior.

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?

It gives a clear usage trigger: 'Call it when the user says "work on my next Stride task"' and explains the staged/assigned fallback. It does not explicitly name alternatives to use instead or when not to use this tool, so it stops short of full when/when-not guidance.

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