get_share_integration_guide

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

No annotations provided, so the description fully bears the burden. It emphasizes that no SDK installation is needed and tap is a global object, which are key behavioral traits. It outlines what the guide covers, but does not describe side effects or output format. Still, it provides adequate transparency for a read-only informational tool.

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 concise with two sentences and bullet points. The front-loading with '⭐ READ THIS FIRST' and emphasis on key points is effective. Every sentence adds value, though the bullet list could be slightly more concise but still reasonable.

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 parameters and no output schema, the description is quite complete: it explains what the tool returns (workflow steps), highlights critical details, and lists covered topics. It could hint at the output format (e.g., textual or structured), but overall it provides sufficient context for an agent to use it appropriately.

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 zero parameters and 100% coverage. Baseline is 4 for no parameters. The description does not need to explain parameters and does not add parameter-specific information, which 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 states the tool returns a complete step-by-step workflow for TapTap Share API integration, specifying verb 'get' and resource 'share integration guide'. It includes a note to read first. However, it does not explicitly differentiate from other integration guides among siblings, but the detail about share API is sufficient.

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 explicitly says to use this when the user wants to integrate/share/setup/add share functionality and to use it before making implementation plans. This provides clear context for when to invoke the tool, though it does not mention when not to use or alternative tools.

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