flutter_get_sample

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

No annotations are provided, so the description carries the full disclosure burden. It doesn't state whether this is read-only, whether it requires any prerequisites (like first calling flutter_list_samples/find_sample to get a valid id), or what happens if the id is invalid/not found. It also doesn't disclose output structure beyond 'complete compilable code and notes.'

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?

Single sentence, zero waste, front-loaded with the core purpose. It's concise and to the point. Could include slightly more usage context, but as a one-sentence description it's efficient.

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 single-parameter tool with a documented schema and no output schema, this is reasonably complete for basic usage. However, it lacks guidance on prerequisite steps (calling list/find first), error handling for bad ids, and since there's no output schema, it would benefit from describing the expected return structure more explicitly.

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 coverage is 100%, with the id parameter well-documented in the schema itself. The description adds little beyond the schema—it doesn't elaborate on id format outside what the schema's example provides. The schema already explains id sources, so the description adds marginal value here.

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 gets a specific sample by id from a corpus, with complete code and notes. The verb+resource is specific (get a sample by id) and the content scope is defined (complete compilable code and notes). It doesn't explicitly differentiate from siblings like flutter_list_samples, but the by-id retrieval is implied distinct from listing.

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 implies this is used to fetch a specific sample by id, and the id parameter references sibling tools (flutter_list_samples, flutter_find_sample) as a source for ids. However, it doesn't explicitly state when to use this vs alternatives, nor does it mention that flutter_list_samples/find_sample should be called first.

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