flowker-discover

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description reinforces this by framing the tool as purely inspect/discover and adds detail about what can be safely inspected. No contradictions with annotations are present.

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 two sentences long, front-loaded with the tool's purpose, and each sentence contributes useful guidance. It avoids redundant restating of the tool name and gets straight to instructions for the agent.

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 discovery tool with rich annotations and a well-described schema, this description provides enough contextual framing about what can be discovered and when to call it. It does not detail output shape or exhaustive edge cases, but given no output schema and the intentionally broad discovery scope, the level of detail is reasonably complete.

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 100%, so the schema already documents all 5 parameters including enums for intent and component. The description adds high-level domain context but does not substantially enrich parameter-level meaning beyond what the schema provides, so a baseline of 3 is appropriate.

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 clearly identifies the tool as a discovery mechanism for Flowker API resources, actions, and execution contracts. It uses specific verbs like 'Discover' and 'inspect' and distinguishes this tool from its execution counterpart flowker-execute by explicitly framing its pre-execution role.

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 provides explicit usage context: 'Use this before flowker-execute' and lists the kinds of things an agent should inspect. It does not explicitly name alternative discovery tools, but it clearly communicates the intended workflow phase and purpose.

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