firestarter_my_markets

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

Annotations already include readOnlyHint=true and destructiveHint=false; the description reinforces this with 'Read-only.' It adds context about the ownership scope (only markets the user created) and the fields returned, which goes beyond the annotations but does not disclose additional operational behavior (e.g., auth details, rate limits).

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 compact yet information-dense: it opens with the core function and fields, then immediately offers usage guidance and alternatives. Every sentence serves a purpose without redundancy.

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 fully covers the return structure and the intended usage. It also clarifies ownership and read-only nature, and points to related tools for adjacent needs, making it complete for an agent to invoke 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?

The input schema has no parameters, so the baseline is 4. The description implies no inputs are needed by stating 'List the community markets you OWN' without mentioning any configuration options. No additional parameter explanation is required.

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 states the action (List) and the resource (community markets the user owns), and enumerates the exact fields returned (program id, buyer-facing name, URL/handle, share code, status, fee share, member count). It also differentiates from siblings by naming specific alternative tools (firestarter_market_earnings, firestarter_market_preview) and their use cases.

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?

Provides explicit when-to-use scenarios ('what markets do I have?', needing program_id, at-a-glance view) and explicitly names alternatives for earnings and preview. The read-only note further clarifies safe usage.

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