tealfabric_get_webapp

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It indicates a read-style retrieval operation and the option to request a specific version, but it does not mention response format, version default behavior, or error conditions. This is acceptable for a simple getter but leaves some room for interpretation.

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?

Two short sentences carry exactly the needed information, with the core operation front-loaded and the optional version behavior stated separately. Every sentence earns its place with no 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?

For a straightforward single-resource getter with two fully documented parameters and no output schema, the description is sufficient for an agent to call the tool correctly. It could mention return behavior, but the operation's simplicity makes that a minor gap.

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 both parameters. The description restates the ID and version concepts but adds no semantics beyond what the schema provides, matching the baseline for fully covered schemas.

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 ('Get'), a resource ('Tealfabric webapp'), and a selection mechanism ('by ID'), clearly distinguishing it from list, create, update, and publish sibling tools. The optional version qualifier adds precision without ambiguity.

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 clearly conveys that this tool is for fetching a single webapp when an ID is known, which implies when to use it over list_webapps or other sibling operations. It does not explicitly name alternatives or exclusion conditions, but the context is clear enough for correct selection.

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